similar to: Syslogd / rc

On 7/24/2017 8:39 PM, Nico Kadel-Garcia wrote: > > Why are the targets of the hardlinks evaporating on rebooting? Is that > a FreeBSD'ism? Its when syslogd stops/starts. The hardlinks need to be recreated for some reason. ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike at sentex.net Providing Internet services since 1994

Dear all! Last evening I've noticed that my 5.2 box had strange result about nmap search. One port is randomly open when I look from user account. From root everything looks as expected. The comp is most time out of internet. The last thing was adding "expect" package. I am not paniced, could be hiting... Or something in "expect" package... It is random port from 53000 to

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

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

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

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

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

--------------------------------------------------------------------- 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, 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

" 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:

Matt -- I actually came up with a much more elegant script. On FreeBSD there is a command 'fstat' (I'm sure this could be modified to use 'lsof' or something of the like). First of all, while liveice and icecast are running properly, # fstat -m | grep liveice |wc -l for me yeilds 56 or 57. I let liveice die and checked again, and that number went significantly down.

There seems to be some discrepancy between rpcclient's man page and "rpcclient --help" in regards to the servername. It seems that the proper usage of rpcclient is rpcclient [options] server this is the format that is specified in "rpcclient --help." rpcclient's man page, however specifies that the servername should come directly after rpcclient. I.E.

I'd love to take a look at this script, and, more than likely, I'm not the only one :) Please post an example. > Liveice definitely needs a keepalive script of some kind. It's tricky, > though - since it can lose connection to the server & stop streaming, but > continue to run. The only truly reliable keepalive I've used polls the > server to see if it says the

could someone please point me to a good icecast log analysis tool? i'm looking for something that generates html based on client IPs and their connect times. thanks in advance. -- ------------------------------------ Robin P. Blanchard IT Program Specialist Georgia Center for Continuing Ed. fon: 706.542.2404 fax: 706.542.6546 email: Robin_Blanchard@gactr.uga.edu

i run the latest CVS versions of: icecast / liveice / lame without problem on freebsd-4.3. > I am very tempted to try and use icecast as the weapon of choice > to realize a live audio stream for the radio station I work for. > > Now, the last time I tried the FreeBSD port of Icecast, it > immediately consumed something like 95% CPU time, even without > any client connected. I

> > Ices will reload the playlist file if it changes on disk. So if the > > file changes every track, everything will be fine. Alternatively you > > could write your MP3 to a FIFO, which ices could pipe to your icecast > > server. > > that looks like an interesting alternative, tho i have no clue how to do > that, and particularly in the context of otto (which,

> If you want something broken and stupid, the original patch you posted > will probably work ok. Change 'while (1) {' to just '{'. > > Being young and naive, I am still surprised when people are willing to > work twice as hard to do things the wrong way, just because they heard > about that way first. > being old and lazy i'm willing to take the easy

> assuming otto can execute an arbitrary shell command whenever the > track plays (I assume it can call whatever mp3 decoder you want), you > can > a) have a script that does something like > echo $1 > /path/to/playlist.txt > Then ices will reload the playlist file (size: one entry) at the end > of the track. > > b) do > mkfifo ices.fifo > echo ices.fifo >

> I'd love to take a look at this script, and, more than likely, I'm not > the only one :) > > Please post an example. > > OK - This is a quick & dirty hack - I'm sure there are several more elegant solutions... But it works. NOTE: this is designed for a Shoutcast server. You'd need to change the check= lines to work with Icecast. Couldn't find an

running: latest CVS of icecast-1.3.11, liveice, and lame. i initially launch the server with the following shell script: #!/bin/sh /usr/local/bin/icecast -c /usr/local/etc/icecast/conf/icecast.conf -b /bin/sleep 5 /usr/local/bin/liveice -F /usr/local/etc/liveice/liveice.cfg >/dev/null 2>/dev/null & everything runs fine for a random period of time (sometimes hours, sometimes days) until