On Wednesday, April 17, 2002, at 11:55 , Chas Owens wrote:
[..]
> Oopsy, forgot the sleep call. That is what I get for just posting code
> without testing it first. Well, I did say something like this <grin
> />. Maybe it should look more like this (actually it shouldn't, you
> _should use cron or the NT equivalent):
[..]
Hugs and Kisses - smooch, smooch, love you any way....
running them from cron means that in the morning there will be
email about what the job did... great for those 'needs to
run around or after midnightish' types of stock sysAddStuff.
Not good for folks who want to have their automation run more
often than once a day, since the spam mail can get annoying.
So the generalized leap towards a deamon was a practicalish
approach towards a generalized solution...
but the moment that I saw the 'fork' there - I got way
worried, since I did not see any of the classics that
i expect when creating a daemon - such as dealing with
the STDIN/STDOUT/STDERR - setting process group Id, et al.
given that you did not provide a means to 'stop' your
almost like a daemon... nor, for that matter provided
the appropriate 'init scriptology' such that it would
always restart on reboot..... and ....
These are some of the simpler bits about getting around
to writing a 'daemon' - in perl or any language - and
folks need to think about the costs and consequences...
and there was NO POD!!!!
Bad, Bad, Bad Chas.... No Cookie....
{ ok, so I have these strict standards about what can
be installed and run as a daemon.... }
ciao
drieux
---
ok, so I have this other crisis - namely the bbedit folks,
the other mailing list I am on, pointed out that there were
these cool tricks I could do with it - and I used it as a,
GASP!
"Perl IDE" - to write, debug, and skank around a bit...
is there an official place to get therapy to help me
deal with the idea of a Perl IDE????
Orthodox Perl, this I Grok,
"Perl IDE".... this hurts...
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
