similar to: Serial Ports and syslogd

Dear list! I have a little problem, trying to enable logging of deny rule. I have enabled it via kernel: options IPFIREWALL options IPFIREWALL_VERBOSE options IPFIREWALL_VERBOSE_LIMIT=3 It is ipfw2. After that, my inten- tion was to use syslogd and !ipfw *.* /var/log/ipfw.log and newsyslog with /var/log/ipfw.log 600 3 100 * J In rc.conf I have firewall_enable="YES"

I made a quick change to syslogd(8) so that it can drop root privileges immediately after starting up. It opens up the log sockets (UNIX and network domains) and writes the PID files before dropping privs. It drops privs before openning log files and writing to users. Therefore, you would need to modify your log file permissions appropriately. As for writing to users, ttys generally are writeable

Package: logcheck Version: 1.2.69 The inetutils-syslogd (2:1.5.dfsg.1-9) package provides a system logging daemon. syslogd periodically logs the following message: Dec 17 00:29:11 host syslogd (GNU inetutils 1.5): restart The following logcheck rulefile works to filter the messages from the "System Events" email: # cat inetutils-syslogd ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ syslogd

Hello! on my centos 4.4 i have enable selinux, but after this change syslogd can't no more run: # /etc/init.d/syslog restart Shutting down kernel logger: [ OK ] Shutting down system logger: [FAILED] Starting system logger: syslogd: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or

Hi all. Bug bin/8865 strikes again? I have a FreeBSD 4.8 Release machine. After sometime, the logs just aren't modified, syslogd just doesn't log. The last entry on /var/log/messages is from may 15. Could this be caused to use a serial console (-P on /boot.config, no keyboard attached) to access the machine? There was once a time that when i Control^D'ed on the serial console and

Hi, There have been several replies on the syslogd question. All 2 to 4 lines long. I therefore gathered them here. Roger. ----------------------------------------------------------------- From: Paul Kenyon <pkenyon@loctech.com> Date: Wed, 24 Jun 1998 11:37:01 -0500 I believe it is possible to pipe anything through SSH. I''ll find the URL to the info and post it. I

Yesterday I activated SELinux in targeted mode, then I rebooted and started receiving some error messages in the system services initialization: ====================================================================== audit(1156518721.252:2): avc: denied { read } for pid=2223 comm="syslogd" name="libc-2.3.4.so" dev=dm-0 ino=50441 scontext=user_u:system_r:syslogd_t

In response to my post regarding core-sdi's secure syslogd - ssyslogd. Sorry it has taken me so long to post this...been super busy... I didn't get a lot of responses back from the list regarding ssyslogd. Just a couple of people who said they were using it, and it was working. I grabbed the latest version (ssyslogd-1.22) from http://www.core-sdi.com/ssyslog/. I had a problem compiling

> > Second, why don''t you implement a "black box" log system ? > > That''s all log generated by all hosts on your network is forwarded > > to a seperate log machine called black box. Such computer grants > > no access to any body whatsoever except for user "root" loginning on > > the console. > > how to setup a

Hi all, I have installed a CentOS4.3 box and migrated some application from FC1 to the new box, everything else runs perfectly except syslogd/klogd. /etc/rc.d/init.d/syslog starts without any problem, but there is nothing logged into /var/log/messages, even I restart the service. However, I tried to shut the service down and run "syslogd -m 0 &" and "klogd -x &" as

Package: logcheck Version: 1.2.32 Severity: wishlist /etc/cron.daily/sysklogd restarts syslogd at the end of the script. This causes a daily log message, currently missed by logcheck: Jan 14 06:55:22 pyloric syslogd 1.4.1#16: restart (remote reception). I'm currently using this regex in ignore.server.d/local-syslogd: ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ syslogd 1\.4\.1#16: restart \(remote

" Message from syslogd at localhost at Aug 27 08:57:53 ... kernel:Disabling IRQ #17" is the message I got on all my terminal windows at the time indicated. What is it complaining about? What should I do about it? I got some information from dmesg. It mentions IRQ 17, but the only error is from before the most recent hibernation. Here are some excerpts, in order from dmesg: SELinux:

Just updated our syslog server to 4.8-STABLE #0: Mon Apr 7 09:39:27 EDT 2003 In my rc.conf I have: # fgrep syslog /etc/rc.conf syslogd_program="/usr/local/sbin/syslog-ng" syslogd_flags="" Syslog-ng starts up appropriately; but syslogd also tries to start now. Since the port's already in use, rc hangs during boot until I ctrl-c at that point. Perhaps something's not

--------------------------------------------------------------------- Red Hat, Inc. Security Advisory Synopsis: Denial of service attack in syslogd Advisory ID: RHSA-1999:055-01 Issue date: 1999-11-19 Updated on: 1999-11-19 Keywords: syslogd sysklogd stream socket Cross references: bugtraq id #809 --------------------------------------------------------------------- 1. Topic: A

Hello happy nuters, Some complementary words about making nut 2.02 successfully run on FreeBSD with MGE Ellipse. With the usefull information Arnaud sent, it's rather obvious that the erratic response of the ups to the shutdown script is linked to its difficulty to handle large traffic on the serial line. These are the final tweak I made to have this configuration satisfyingly

Hello, My entry for newsyslog in /etc/crontab is: 0 * * * * root newsyslog -t \%Y-\%m-\%d_\%H:\%M And I get: newsyslog: Could not convert time string to time value: No such file or directory I try to use the newsyslog from head to to avail. This solution was working a month ago (see Revision 248776) My file system is zfs version 28. Henri

Hi Has anyone got a Compaq(/HP) T700 UPS to work with the BCMXCP driver? I've built yesterday's CVS of NUT 2.1 on one of my FreeBSD systems but chown root:wheel /dev/cuaa0 /usr/local/libexec/upsdrvctl -u root start gives: -- Network UPS Tools - UPS driver controller 2.1.0 Network UPS Tools - BCMXCP UPS driver 0.10 (2.1.0) Communications with UPS lost: Error executing command

Well, 4 days after previous upgrade i cvs'ed RELENG_4 from local cvs tree (updated hourly), made buildworld buildkernel installkernel, rebooted into single user, made installworld and mergemaster. Mergemaster updated newsyslog.conf, syslogd.conf, ok, rebooted... Wow... All scripts from /usr/local/etc/rc.d refused to load. And the system is in "Amnesiac" mode Attempt to run

Hello nuters, FreeBSD, Ellipse USBS 800, serial line, nut 2.02 everything works fine. But I'm only able to get an automatic shutdown when reaching the built-in 30% level. I the "lowbatt parameter" is set to anything, it's simply ignored. This is a problem as I want to shutdown around 90% to avoid the battery to drain out when multiple shutdowns occur. Any idea ?

I'm running a few servers sitting on top of a NetAPP file server ? everything runs great, but periodically I'm getting: nfs_getpages: error 13 vm_fault: pager read error, pid 11355 (https) errors on my screen ? not always same pid ? the annoying part is that it seems to always affect the same jail that is running .. if I shutdown all jails on that physical server, everything shuts down