steveluxmoore
Programmer
Hi all,
I believe I have a unique quiry with the syslog and am wits end. Enjoy.
Given a logger -p kern.err "Hi there" command from super user and an entry in /etc/syslog.conf to copy all log messages to an indepentant log file, (I have also tried to /dev/console);
*err;*.notice;*.debug;*.info;*warning;*.alert;*.crit;*.emerg /var/adm/temp_messages
the message does not get logged. Please note that other messages eg, logger -p mail.crit "Hi there" work like a gem. It seams it is only with kern messages.
I've read some where that user programs can not send kern messages, so I'd written a simple driver to add_drv -v dummy_drv it. Still no kern entries in the log file.
I've tried booting the kernel (I might add it's on a Sparc platform) in verbose mode, eg, ok boot -v still no luck.
Any hints??
I believe I have a unique quiry with the syslog and am wits end. Enjoy.
Given a logger -p kern.err "Hi there" command from super user and an entry in /etc/syslog.conf to copy all log messages to an indepentant log file, (I have also tried to /dev/console);
*err;*.notice;*.debug;*.info;*warning;*.alert;*.crit;*.emerg /var/adm/temp_messages
the message does not get logged. Please note that other messages eg, logger -p mail.crit "Hi there" work like a gem. It seams it is only with kern messages.
I've read some where that user programs can not send kern messages, so I'd written a simple driver to add_drv -v dummy_drv it. Still no kern entries in the log file.
I've tried booting the kernel (I might add it's on a Sparc platform) in verbose mode, eg, ok boot -v still no luck.
Any hints??