similar to: Syslogd and serial console bug?

Hello, It's a bit off topic, but I'm hoping someone has seen this before. I'm running a couple of headless boxes, one is 4.7 release, the other is 4.8 release. Both have the same issue with newsyslog when I've got the serial port enabled for console management. (-h in boot.conf and a getty running on cuaa0 after the boot process) Logrotate tries to send an HUP to syslogd, but

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

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

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

Hi, I'm running into an issue while using FreeBSD 5.4, NUT from ports (2.0.3), serial on /dev/cuaa1, Ellipse 1200 USBS. The ups.conf is : [ellipse] driver=mge-utalk port=/dev/cuaa1 desc="Telecom Closet Ellipse" When I go to start it I get : Network UPS Tools - UPS driver controller 2.0.3 Network UPS Tools - MGE UPS SYSTEMS/U-Talk driver 0.87 (2.0.3)

Hi, FreeBSD 5.4, NUT from ports (2.0.3), serial on /dev/cuaa1, Ellipse 1200 USBS. I set the ups.conf up as : [ellipse] driver=mge-utalk port=/dev/cuaa1 desc="Ellipse" When I go to start it I get : Network UPS Tools - UPS driver controller 2.0.3 Network UPS Tools - MGE UPS SYSTEMS/U-Talk driver 0.87 (2.0.3) Could not get multiplier table: using raw

Hi Stefanos, I've forwarded your mail to the nut user mailing list, which is the right place to get support. thanks to subscribe to it (http://alioth.debian.org/mail/?group_id=30602). Arnaud -- Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ OpenSource

Some one might have answerd this, but I can not find any think yet I am trying to load a SOLA 610 700va ups up and keep getting : --------------------------------- Network UPS Tools - UPS driver controller 2.0.5 Network UPS Tools - MGE UPS SYSTEMS/U-Talk driver 0.88 (2.0.5) .Detected Pulsar ESV11+ on /dev/cuaa0 Network UPS Tools - Best UPS driver 1.03 (2.0.5) Unknown model detected - please

Hi, All ! I'm trying to use nut 2.0.5 on FreeBSD 4.11-STABLE with UPS INELT Monolith II 1000LT UPS connected to box with RS-232 cable. In ups.conf: [apc] driver = megatec port = /dev/cuaa1 desc = "UPS" When starting /usr/local/etc/rc.d/nut.sh start got: Network UPS Tools - UPS driver controller 2.0.5 Network UPS Tools - Megatec protocol driver 1.5 (2.0.5) Carlos Rodrigues (c)

Hi guys, I was playing on vmware with btrfs on complete disks /dev/sd{b,c,d,e}. Next I decided to use partitions, so I created /dev/sd{b,c,d,e}1 and used those, worked fine! Afterward, I mistakenly re-ran an old command on the full disk ( mount -t btrfs -o subvol=. /dev/sdb /mnt/ ) notice this is sdb not sdb1, and I got this spectacular kernel freeze. Let me know if that''s some bug.

Package: xen-hypervisor-3.0.3-1-i386-pae Version: 3.0.3-0-2 Hi! the error suddenly appeared when rebooting one of the etch instances using xm reboot <name> on our etch server DEVIDE:~# DEVIDE kernel: ------------[ cut here ]------------ DEVIDE kernel: CPU: 3 DEVIDE:~# Message from syslogd@DEVIDE at Tue May 8 11:45:27 2007 ... Message from syslogd@DEVIDE at Tue May 8 11:45:27 2007