search for: semyonov

...for 2 hours. The summarized time, the mount was listened for, is 3*3+2*1+1*2=13 hours. Than, some time later, using such a statistics, I point less popular mounts. Does anybody know, if there is such an embedded feature in icecast2, or any add-on code, that helps doing so? Best regards, Andrey V. Semyonov

Package: logcheck-database Version: 1.2.68 Severity: minor openssh-server version 1:5.1p1-2 ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ sshd\[[0-9]+\]: reverse mapping checking getaddrinfo for [._[:alnum:]-]+ failed - POSSIBLE BREAK-?IN ATTEMPT!$ should look like ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ sshd\[[0-9]+\]: reverse mapping checking getaddrinfo for [._[:alnum:]-]+ \[[.[:alnum:]:]+\] failed -

On Mon, 4 Feb 2008 08:15:24 +1300, martin f krafft wrote: > logcheck has the policy not to ignore restart messages. Thanks for > the patch, please understand that I won't be including it. Quote from README.logcheck-database: "Unfortunately, we don't have the time to add and update rules for everything, therefore the following exceptions apply: * Debug messages * Messages

Hi, I am the current webmaster at WUML (www.wuml.org) a college radio station. We are looking to purchase a new web cast server which we are planning will run IceCast, but it is a little unclear on the system requirements that IceCast requires. I read somewhere that IceCast can run on as little as a 486 with 32mb of ram but that sounded like those specs were for streaming mp3s saved on that

Monday, July 12, 2004, 4:49:57 Michael Smith wrote: MS> You should be able to get this information from the access logs. There's no MS> software I know of to do that automatically for you, though - you might have MS> to write your own. As I understand, access logs do not contain any informatin about the time a listener has been connected for. But I found such an internal variable in

Hi, I have the following system configuration (probably does not matter, but anyway): Ubuntu Linux x86 VM running under ESXi bare metal hypervisor. UPS is connected to the ESXi host, and VM communicates to the UPS using USB pass through option. Details of elaborated shutdown sequence are out of topic, so I skip them. NUT was installed from the package, I believe it is recent enough. NUT was set