On Tuesday, August 13, 2002, at 07:33 , Kipp, James wrote:
[..]
>> a couple of basic concerns.....
>>
>> a) your redirect of STDERR, STDOUT
>> means that you will be losing all of your
[..]
> Hopefully there won't be any :-). Your right, i was aiming to change that.
as we say -
a) checks in the mail
b) respect you in the morning
c) staffing your proposal
d) that looks 'fabulous' on you....
.....
[..]
>> b) it is not clear to me, from this segment, that you are
>> laying a PIDFILE to simplify the method by which you
>> do the simple 'shutdown' of daemons by sending them a
>> signal....
>
> not sure what you mean here. are you saying that i should incorporate some
> code to shut down the daemon nicely if needed?
my basic daemon 101 kult is
daemon_critter -c <config_file> :- create one
daemon_critter -k <config_file> :- kill this one
daemon_critter -r <config_file> :- reload config info
because I am accustom to having a 'single piece of code' -
this "daemon_critter" that will do unique stuff... based
upon the <config_file> it is handled.... some folks notice
that it is possible to "hide" that detail by allowing for
a "config_dir" to be a pre-assigned value hence one can have
a single way of solving this with
daemon_critter start
daemon_critter stop
daemon_critter hup
{ or some other appropriate verb } - at which point it dashes
off to its $HOME/config_dir and in essence invokes
for conf in *.conf
do
daemon_critter $verb $conf
done
and thus the init scriptology on a sys_V style box is way
pathetically simplistic...
> Thanks for chiming in here. right now the deamon is running fine (i did
> change the STDERR and STDOUT output to a err file), but i am still nervous
> about it :-)
when there are no problems,
everything is Wonderful....
ciao
drieux
---
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
