Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 30974 - fcron ebuild suggestion
Summary: fcron ebuild suggestion
Status: RESOLVED UPSTREAM
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High enhancement
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-12 09:40 UTC by Pawel
Modified: 2004-10-02 23:14 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pawel 2003-10-12 09:40:12 UTC
Hello,

May I suggest adding the following line to the fcron ebuild, between econf and
emake?
sed s/-Ffcron/-Ffcron.$HOSTNAME/ config.h > config.h.2 && mv config.h.2 config.h

When fcron sends emails the sender's name is set as "fcron", the above addition
will set it as "fcron.$HOSTNAME". This comes in handy for sorting and quickly
identifying which host the email originated on.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Comment 1 Matthew Kennedy (RETIRED) gentoo-dev 2003-10-22 13:38:42 UTC
hi, is it such a good idea to hard code the hostname like that at compile
time?>
Comment 2 Pawel 2003-10-22 16:13:21 UTC
you're right, I did not consider the fact that some people are using precompiled
packages. I guess patching fcron so it takes that as an argument is the better
way to go.
Comment 3 Seemant Kulleen (RETIRED) gentoo-dev 2004-03-26 11:33:56 UTC
folks -- do we have a patch forthcoming then?
Comment 4 SpanKY gentoo-dev 2004-04-18 15:23:37 UTC
i just added fcron-2.9.4 ... i'm not *too* familiar with its configuration setup, but could you see if it's possible with this new version ?
Comment 5 SpanKY gentoo-dev 2004-10-02 23:14:46 UTC
actually, this isnt a clean solution

the $HOSTNAME will be replaced with whatever machine fcron was built on ... if you build a binary package and use it on other machines, they will all be using the $HOSTNAME of whatever machine it was built on

the required solution here is to have fcron grab $HOSTNAME either from the environment or via the C function gethostname()

if you develop a patch to handle that i'll gladly add it ... or just ask upstream to do it ;)