Andrew Curry schreef:
> the problem with a daemon is you need to keep checking its
> running
google: inittab respawn telinit
--
Affijn, Ruud
"Gewoon is een tijger."
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
http://learn.perl.org/
me testing
regarding performance and maintenance from what Andrew said.
Cheers,
Toddy Prawiraharjo
-Original Message-
From: Chas Owens [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 08, 2007 10:36 PM
To: Andrew Curry
Cc: [EMAIL PROTECTED]; beginners@perl.org
Subject: Re: run perl a
nces
(should it take over a minute).
-Original Message-
From: Chas Owens [mailto:[EMAIL PROTECTED]
Sent: 08 August 2007 13:36
To: Andrew Curry
Cc: [EMAIL PROTECTED]; beginners@perl.org
Subject: Re: run perl as service
On 8/8/07, Andrew Curry <[EMAIL PROTECTED]> wrote:
> To be hon
On 8/8/07, Andrew Curry <[EMAIL PROTECTED]> wrote:
> To be honest in terms of database monitoring cron is usually the way to go.
> The advantage Is that then you don't need to monitor the monitoring program.
> As a DBA you need reliable data in terms of status etc... You could write an
> overcompli
On 8/8/07, Toddy Prawiraharjo <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I wrote a simple perl script to check some variables in SHOW STATUS in a
> mysql server. Now, how do I run it as a service/daemon?
> I want more flexibility than crontab which is based on time. Should I use
> sleep? Or is there
-Original Message-
>From: Toddy Prawiraharjo <[EMAIL PROTECTED]>
>Sent: Aug 8, 2007 8:12 PM
>To: beginners@perl.org
>Subject: run perl as service
>
>Hi all,
>
>I wrote a simple perl script to check some variables in SHOW STATUS in a
>mysql server. Now, how do I run it as a service/daemon
To be honest in terms of database monitoring cron is usually the way to go.
The advantage Is that then you don't need to monitor the monitoring program.
As a DBA you need reliable data in terms of status etc... You could write an
overcomplicated daemon which monitors its state but if cron is an opt
