/me considers recoding the whole thing as a cronjob...
(A joke, in reality I simply don't have the diskspace to put cron where
this is needed so it's not an option even if it COULD do the work).
Interesting, I have since learned something else.
In fact it DOES work - but there is an odd
Well one difference between running the init script from shell and during boot is the environment. Are you using some shell commands or something else for let say GetDirList, because during boot the path variable is not initialized as it is when you are in shell (actually I think it is empty) and
Hi all,
I have written a daemon as part of a project (I used the daemon.pp example as
a skeleton), it's working quite perfectly if you start it from the
commandline, including from the bootscript I wrote.
But when started at boottime it doesn't operate correctly anymore.
The timer still counts
Am Donnerstag, 1. Juni 2006 22:40 schrieb A.J. Venter:
Hi all,
I have written a daemon as part of a project (I used the daemon.pp
example as a skeleton), it's working quite perfectly if you start it
from the commandline, including from the bootscript I wrote.
But when started at boottime it
Any idea where I should start looking ?
Just a shot into the dark: maybe you start yout deamon, before your
local timezone is set up?
Does it change anything, when you move your bootscript to a higher
position in rc.x, e.g. make it S99whatever?
Good theory, but my daemon is very nearly the
A.J. Venter wrote:
Any idea where I should start looking ?
Just a shot into the dark: maybe you start yout deamon, before your
local timezone is set up?
Does it change anything, when you move your bootscript to a higher
position in rc.x, e.g. make it S99whatever?
Good theory, but
Just my 2 cents: If you're on linux look at the file rw permissions,
especially for I/O-interfaces like ttyS0, ttyS1, etc. In Fedora they
have only root write permissions.
Joep
Well as far as I know I'm not writing to anything except the log file, and the
daemon is running as root anyway.
