My department has several linux computers and auditing the logs is very tiresome if they are all localized to each computer. While the vanilla syslog offers remote logging features it uses udp and thus many things can affect the chance of log messages reaching their destination. the message dropping problem is not as widespread in syslog-ng since it uses tcp to transmit log packets.

Compiling syslog-ng is required as the only syslog-ng binaries are licensed and require a contract to purchase. under rhel/centos the eventlog compilation goes as planed, but things start going wrong when auto configuring syslog-ng itself. it will complain. configure: error: Cannot find eventlog version >= 0.2: is pkg-config in path? this is a easy problem that can be fixed with running configure in the following way:

PKG_CONFIG_PATH=/usr/local/lib/pkgconfig ./configure –sysconfdir=/etc

this causes the syslog-ng.conf file to go to /etc/syslog-ng.conf and adhere to the layout choices of rhel/centos. ... Read More

linux server: leif

solaris client: sisu

export the shares on leif to sisu and then exportfs -r

add an entry in /etc/hosts.allow on leif

on sisu modify the file /etc/auto_master and add the line

/- auto_direct

in /etc/auto_direct add lines like

/home -rw leif:/home

reboot and celebrate

if that is working its now time to set up nis to get remote logins

first set up the domainname in /etc/defaultdomain and use the domainname tool to set it

Create a directory named /var/yp/binding/domain

3. If you want the NIS client to broadcast for a NIS server (note: there must be a NIS server on your subnet), start NIS with /usr/lib/netsvc/yp/ypstart. If you want to manually specify one or more NIS server(s) to use, run ypinit -c and then /usr/lib/netsvc/yp/ypstart. Note that each manually specified NIS server must have an entry in ... Read More