On Thu, Aug 03, 2000 at 06:08:10PM -0700, Ian Lance Taylor wrote:
> svscan simply creates a pipe. That is, it redirects stdout of ./run
> to stdin of ./log/run. It doesn't do anything with stderr. If your
> program logs to stderr, then 2>&1 in ./run will redirect the logs to
> the stdout of ./r
Date: Thu, 3 Aug 2000 20:58:26 -0400
From: Adam McKenna <[EMAIL PROTECTED]>
I am pretty sure svscan expects the logging to come through on a certain file
descriptor, but not positive. Does anyone know if this is the case? If so,
which one is it? Should I just add a 2>&1 at the e
I've been having problems running sslwrap out of inetd so I decided to run it
via tcpserver instead.. I'm using svscan. But for some reason, the logs
refuse to go to /var/log/qmail/ssl/.
Here's my "run" file:
#!/bin/sh
PATH=$PATH:/var/qmail/bin:/usr/local/bin
exec /usr/local/bin/softlimit -m
