On Thu, 25 Sep 2003 16:19:18 -0500 "Brett Franck" <[EMAIL PROTECTED]> wrote:
> If it is possible, how would you map say UDP port 515 to syslog and have
> syslog report it to a specific logfile through the syslog.conf file?
Hi Brett,
Here's one way to do it using the standard syslogd:
Attached is a script file that will build a chroot environment
for the syslogd command. Run this "build" script to create
a subdirectory with everything you need to run another
copy of syslogd on a separate port.
# ./build syslog2 2222
CD into the "syslog2" subdirectory and run the "./go" script to
start a syslogd daemon listening on port 2222 (port 515 is
reserved for printer, check your /etc/services file):
# cd syslog2
# ./go
You can create and run as many copies of this chroot
environment as you like. You'll find a log file under each
directory you create as "./var/log/all.log". You can tweak
the files under "./etc" to configure the logging and port no.
I just whipped this together over a coffee this morning so no
guarantees at all, but it looks simple enough that it should run
for you. If you hit any snags, happy to help.
Good Luck,
Sean
P.S. The build script will create the following
directory structure, and copy/create proper files:
syslog2
|-- dev
|-- etc
| |-- nsswitch.conf
| |-- services
| `-- syslog.conf
|-- go
|-- lib
| |-- ld-linux.so.2
| |-- libnss_files.so.2
| `-- tls
| `-- libc.so.6
|-- sbin
| `-- syslogd
`-- var
|-- log
`-- run
build
Description: Binary data
