W3C Logfile Not Created

Thundermutt · 24th May 2002, 15:28

I have my sc_serv.conf file configured thusly:

W3CEnable=Yes

W3CLog=sc_w3c.log

But for some reason, the sc_w3c.log file is not being created. Well, it actually had been created once before, but after processing the log with the Urchin analyzer (which produced no results, by the way), the log was automatically purged but did not get recreated.

What could be causing this?

Tom · 25th May 2002, 03:04

How long has it been gone? I think it will recreate it when the DNAS detects a title change (at least that is what seemed to trigger the creation under Windows, I didn't look on my Linux box).

Tom

Thundermutt · 26th May 2002, 22:07

You're right, it did recreate it once a new track was loaded. That's kinda weird. So, if I was just looping the same track and my log somehow got deleted, it wouldn't be recreated, even when someone new logs in to listen? Is this a glitch or just the way it works? Thanks for the reply.

jakobn · 30th January 2005, 05:44

Same thing happened to me. w3c.log doesnt update.

I erased the log file and recreated a new sc_w3c.log file using VI editor in Linux. I also copied the first three lines from the log file to the new.

I noted from the README.txt that its possible to restart the log files using kill -HUP or kill -WINCH.

How do I use the kill command? from shell or inside a /bin/bash program ?

Please help

Jakob
Suite108
jakob@suite108.com

Jay · 30th January 2005, 10:51

at the shell just type:
kill -s SIGHUP <pid>

man kill for more information, you can also do
killall -s SIGHUP sc_serv, this signals all of your shoutcast servers.

24th May 2002, 15:28	#1
Thundermutt Junior Member Join Date: May 2002 Location: Marietta, OH Posts: 4	W3C Logfile Not Created I have my sc_serv.conf file configured thusly: W3CEnable=Yes W3CLog=sc_w3c.log But for some reason, the sc_w3c.log file is not being created. Well, it actually had been created once before, but after processing the log with the Urchin analyzer (which produced no results, by the way), the log was automatically purged but did not get recreated. What could be causing this?

30th January 2005, 05:44	#4
jakobn Junior Member Join Date: Sep 2003 Location: Los Angeles Posts: 21	w3c.log Same thing happened to me. w3c.log doesnt update. I erased the log file and recreated a new sc_w3c.log file using VI editor in Linux. I also copied the first three lines from the log file to the new. I noted from the README.txt that its possible to restart the log files using kill -HUP or kill -WINCH. How do I use the kill command? from shell or inside a /bin/bash program ? Please help Jakob Suite108 jakob@suite108.com

30th January 2005, 10:51	#5
Jay Moderator Alumni Join Date: May 2000 Location: Next Door Posts: 8,942	at the shell just type: kill -s SIGHUP <pid> man kill for more information, you can also do killall -s SIGHUP sc_serv, this signals all of your shoutcast servers. -Jay \| Radio Toolbox.com

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Switch to Linear Mode Hybrid Mode Switch to Threaded Mode

25th May 2002, 03:04	#2
Tom Moderator Join Date: Apr 2000 Posts: 4,491	How long has it been gone? I think it will recreate it when the DNAS detects a title change (at least that is what seemed to trigger the creation under Windows, I didn't look on my Linux box). Tom

26th May 2002, 22:07	#3
Thundermutt Junior Member Join Date: May 2002 Location: Marietta, OH Posts: 4	You're right, it did recreate it once a new track was loaded. That's kinda weird. So, if I was just looping the same track and my log somehow got deleted, it wouldn't be recreated, even when someone new logs in to listen? Is this a glitch or just the way it works? Thanks for the reply.