Am 11.06.2014 13:04, schrieb Paul Alfille:
>
> Also, in the documentation about systemd, there was a long passage about
> how the daemonizing should be done external to the program -- is that still
> the recommended policy? I guess the early testing could help there.
>
Yeah, that's one of the key features of systemd. "I daemonize you, you
don't". The reason is by letting systemd daemonize the process it gets
better control on the logging and situations when the child fails later
on. This is often handled poorly by server applications and each of
these re-implementations of daemonizing fails at some untested situations.
owserver e.g. silently fails when the configured host adapter ist not
present at the very beginning. Later on, it's not a problem when the
host adapter goes missing - there's a technical reason for that
behaviour, but from the admin's perspective, this is very odd behaviour
which needs extra work to polish out.
Kind regards
Jan
------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
