comment on

I prefer daemontools for background processes, as explained in Re: keep a module in shared memory. No need to add a single line of code to your script, no race conditions when handling PID files (because daemontools do not need PID files), and a simple control mechanism. Just write a char to a pipe or let the svc utility do that for you.

(And yes, djb's behaviour regarding errno is just silly and childish. Apply the patch from thedjbway.org or complain loudly to djb that he does not want to accept the C standards. And by the way, also apply the other patch that adds support for SIGQUIT, SIGUSR1, and SIGUSR2.)

Alexander

--
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)

In reply to Re: Executing script in normal/daemon mode and adding start/stop capability by afoken
in thread Executing script in normal/daemon mode and adding start/stop capability by chanakya

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Clear questions and runnable code get the best and fastest answer
	PerlMonks