, but it's better (more secure)
to run a program which just transfers log file entries.
Sorry to reply to this thread so late, I'm catching up on old list
mail.
It would be very much more secure to use SSH. Just create a
'logselect' user on the system holding the logs. Use the 'command='
qualifier
they want.
Sean Truman
www.prodigysolutions.com
[EMAIL PROTECTED]
- Original Message -
From: Russell Nelson [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, August 20, 2000 12:15 AM
Subject: Re: logselect
Ben Beuchler writes:
On Fri, Aug 11, 2000 at 11:45:58PM -0400, Russell Nelson
Ben Beuchler writes:
On Fri, Aug 11, 2000 at 11:45:58PM -0400, Russell Nelson wrote:
I've released my logselect program as a patch to daemontools-0.70.
I'm sorry if this seems like a silly question, but what is the intended
uuse for this program? Remote log retrieval?
Yes. I've
I've released my logselect program as a patch to daemontools-0.70.
It's at http://www.qmail.org/logselect-0.70.patch . If you guessed
that logselect was used to select parts of a log, you're a happy
winner! It's intended to be used in a multi-server environment. By
itself it is of little use
On Fri, Aug 11, 2000 at 11:45:58PM -0400, Russell Nelson wrote:
#!/bin/sh
QMAILDUID=`id -u qmaill`
NOFILESGID=`id -g qmaill`
exec softlimit -m 200 \
tcpserver -p -x cdb -u QMAILDUID -g $NOFILESGID 0 642 \
/usr/local/bin/xargs -e EOF /usr/local/bin/logselect
I thought I'd just nitpick
