Re: script meant to act as daemon dies unexpectedly

in reply to script meant to act as daemon dies unexpectedly

Does your script maintain a persistant connection to MySQL (or any other applications) or does it make a new connection every time? If it does have presistant connections it could be that the connection is breaking (from the other side) and that is killing your application. Have you tried running your application as a command line process (not a daemon) and seeing if it reports any errors when it dies?

Comment on Re: script meant to act as daemon dies unexpectedly

Replies are listed 'Best First'.
RE: Re: script meant to act as daemon dies unexpectedly by Anonymous Monk on May 06, 2000 at 01:04 UTC
We've run it from the command line and even in the Windows environment to see if it behaves differently. It is not a persistent connection to the database, and on my personal linux box it hasn't died yet. It's just occuring on the actual server (which the sysadmins have restricted access to so that I can't run it as commandline there). There aren't any differences between the OS's, so I'm going to have to dig a little on it. Thanks...	[reply]

Replies are listed 'Best First'.

RE: Re: script meant to act as daemon dies unexpectedly
by Anonymous Monk on May 06, 2000 at 01:04 UTC

We've run it from the command line and even in the Windows environment to see if it behaves differently. It is not a persistent connection to the database, and on my personal linux box it hasn't died yet. It's just occuring on the actual server (which the sysadmins have restricted access to so that I can't run it as commandline there). There aren't any differences between the OS's, so I'm going to have to dig a little on it. Thanks...

[reply]

In Section Seekers of Perl Wisdom