search for: syslogd_options

...ding no AllowTcpForwarding no ForceCommand internal-sftp -f LOCAL0 -l VERBOSE Match I am able to access internal-sftp and run sftp sessions properly. But, I am not able to capture the loggings written by internal-sftp process. My syslog config settings are /etc/syslog/syslog ================== SYSLOGD_OPTIONS="-m 0 -a /sftp/sftp.log.socket" syslog.conf =========== In addition, syslog.conf has local7.debug /var/log/sftp.log # Save boot messages also to boot.log local7.* /var/log/boot.log I am running Red...

...Thanks 1. [root at bart ~]# cat /etc/sysconfig/syslog # Options to syslogd # -m 0 disables 'MARK' messages. # -r enables logging from remote machines # -x disables DNS lookups on messages recieved with -r # See syslogd(8) for more details SYSLOGD_OPTIONS="-m0 -r" # Options to klogd # -2 prints all kernel oops messages twice; once for klogd to decode, and # once for processing with 'ksymoops' # -x disables all klogd processing of oops messages entirely # See klogd(8) for more details KLOGD_OPTIONS="-x" # SYSLOG_UMASK=0...

I have a 64bit centos 5.2 system. My router supports sending logs to a syslog server, so I was hoping to send them to my centos box so they are easier to keep an eye on. I've been googling for howto's etc, but I didn't think syslog would be that difficult. Do I need to use syslog-ng or can I use the syslog that's installed with centos 5.2? Any suggestions or guidance? Thanks,

...Does anyone know how to enable the mark facility on CentOS? According to what I was seeing, unlike Debian GNU/Linux, which uses rsyslog, CentOS still uses the traditional syslog where the parameters to be passed to the daemon are taken from /etc/sysconfig/syslog and the default configuration is: SYSLOGD_OPTIONS="-m 0" So, no time stamps are added. As I watched in the man pages for syslog, I tried removing the zero assuming it would take the default of 20 minutes, but I get a error message suggesting to put a numerical value following the "-m". I tried also with "-m 20" and...

I just noticed that on one CentOS 5 server the logs messages, maillog and a couple of others have been blank for a couple of weeks! I tracked down the error to /etc/sysconfig/rsyslogd There was a line SYSLOGD_OPTIONS="-c3" I googled that -c3 defines the "version" or "compatibility mode", and with 3 it means "rsyslog v3 native interface". When I removed the option and restarted rsyslogd, the logging began to work again. I wonder why is this. Probably this was caused b...