From: Tavis R. <ta...@ca...> - 2001-08-31 17:21:28
|
Ben, I think the problem you're experiencing is related to stderr rather than stdout. Either way, this should fix it: Monitor.py start daemon &> webware_output.txt or Monitor.py ... > webware.out 2>webware.err Tavis |
From: <pa...@bo...> - 2001-09-03 08:26:47
|
"Ben Parker" <be...@th...> wrote: > >I can't seem to get Monitor.py to work as a daemon. I am running >"Monitor.py start daemon" via a SSH session. Everything is great until I >close the SSH session, then the AppServer won't respond. I'm assuming this >is because it's execution is tied to stdout somehow. [...] >Sorry for making my OS issue into a Webware issue. This did the trick for >me: > >Monitor.py start daemon > .appserver.log 2>&1 Has anyone looked into "circular logging" with Webware? I've heard that on Linux, at least, there are certain system logging mechanisms which offer such capabilities provided one uses the API concerned. From what I've been made aware of, circular logs only keep information for a certain period of time through the oldest information being continuously overwritten. This strategy should avoid the continual growth of log files which end up filling the filesystem because no-one remembered to check and delete them. ;-) Paul -- Get your firstname@lastname email for FREE at http://Nameplanet.com/?su |
From: Ben P. <be...@th...> - 2001-09-03 09:03:34
|
>Has anyone looked into "circular logging" with Webware? I've heard that on >Linux, at least, there are certain system logging mechanisms which offer such >capabilities provided one uses the API concerned. From what I've been made >aware of, circular logs only keep information for a certain period of time >through the oldest information being continuously overwritten. This strategy >should avoid the continual growth of log files which end up filling the >filesystem because no-one remembered to check and delete them. ;-) > >Paul It happens that there is a very nice set of tools used for managing Qmail that fit this need perfectly. Check out http://cr.yp.to/daemontools written by Dan Bernstein, author of qmail. This is for Unix systems only, including Linux of course. There is a "multilog" tool that listens to a feed from stdin and logs it in a circular fashion. You can easily configure file sizes and number of files in the rotation. The oldest file is dropped as the current file reaches it's limit, assuming the number of old log files has maxed out. Auto-timestamping is optional. Anyone who's installed qmail recently should be familiar with the daemontools system. For others who haven't, the entire package is an interesting alternative to the standard rc.local daemon structure. I'm going to try this system for running/logging my webware appservers as daemon services. |
From: <ir...@ms...> - 2001-09-03 09:09:19
|
On Mon, Sep 03, 2001 at 08:26:42AM -0000, pa...@bo... wrote: > Has anyone looked into "circular logging" with Webware? I've heard that on > Linux, at least, there are certain system logging mechanisms which offer such > capabilities provided one uses the API concerned. From what I've been made > aware of, circular logs only keep information for a certain period of time > through the oldest information being continuously overwritten. This strategy > should avoid the continual growth of log files which end up filling the > filesystem because no-one remembered to check and delete them. ;-) There's a program 'logrotate' which does this. According to the Debian package, "It was downloaded from your friendly redhat mirror. Upstream authors are various redhat people. Copyright: GPL." It runs as a daily cron job and has a config file that specifies which files should be rotated, how many levels, whether to compress, etc. There's an "include" directive to specify a directory containing other config files; this gives a place to put package-specific config files. -- -Mike (Iron) Orr, ir...@ms... (if mail problems: ms...@ji...) http://iron.cx/ English * Esperanto * Russkiy * Deutsch * Espan~ol |
From: <ir...@ms...> - 2001-08-31 22:50:39
|
On Fri, Aug 31, 2001 at 10:29:00AM -0700, Tavis Rudd wrote: > Ben, > > I think the problem you're experiencing is related to > stderr rather than stdout. Either way, this should fix it: > > Monitor.py start daemon &> webware_output.txt > or > Monitor.py ... > webware.out 2>webware.err Shouldn't that first one be ">&" (for csh and tcsh), not "&>". The second would be for bash, sh, ksh, zsh, etc... -- -Mike (Iron) Orr, ir...@ms... (if mail problems: ms...@ji...) http://iron.cx/ English * Esperanto * Russkiy * Deutsch * Espan~ol |