search for: 28192

Thanks for your answer Chris. Nevertheless I just can't see the event you're talking about in my access.log file. I mean the time of the end of listening for each user and the amount of bytes transfered ! Maybe because I'm just a beginner in IceCast... Could you give me an example of a log file (just a part) that shows this notification ? For example on my ShoutCast log tells me :

Howdy, We occassionally get the following error when running our nightly backups: rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229) This happens more on one or two machines than on any of the others. We've looked high and low to see if we're mistakenly sending these signals, but nothing is that we can find. Does anyone know what this might be from? Is it the server

...Priority: P2 Component: sshd AssignedTo: bitbucket at mindrot.org ReportedBy: jan.iven at cern.ch Errors on the initial protocol message do not log the IP of the sender anymore. I.e. doing $ echo "GOOD MORNING" >/dev/tcp/somehost.somedomain/22 results in sshd[28192]: Bad protocol version identification 'GOOD MORNING' from UNKNOWN This appears to be due to the fact that sock_in gets closed before get_remote_ipaddr() has a chance to find out who is at the remote end. Apparently, this worked somehow at least in openssh-3.6p1, perhaps the IP caching was...

...# ifconfig (reduced output) intbr1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:169 errors:0 dropped:0 overruns:0 frame:0 TX packets:85 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1458368 (1.3 Mb) TX bytes:28192 (27.5 Kb) vif2.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:600 errors:0 dropped:0 overruns:0 frame:0 TX packets:612 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:751740 (734.1 Kb) TX bytes:757842 (...