| View previous topic :: View next topic |
| Author |
Message |
MoeRadio.ru
Joined: 28 Jan 2007
Posts: 12
Location: Moscow, Russia
|
 Posted: Tue Dec 23, 2008 9:23 pm Post subject: kill -HUP seem not to work |
 |
|
Hi,
Is there any limitation to kill -HUP?
When I add a new mountpoint and do a kill -HUP `cat /var/run/icecast/icecast.pid` to reload config file, it seems not to see the changes.
When I do a full shutdown/restart, it works fine.
Could be there a problem with the size of /etc/icecast.xml file?
It is 631k in my case with 18861 lines and 3131 mount points (and growing). |
|
| Back to top |
|
 |
karlH
Code Warrior
Joined: 13 Jun 2005
Posts: 5476
Location: UK
|
| Posted: Wed Dec 24, 2008 1:11 am Post subject: |
|
|
that is a lot of mount definitions, but there is no internal limit for those and afaik there is no limit in the xml processing as that would also be a problem with a full restart. The usual issue with failure to re-read over HUP is chroot/chown settings. Check the error log for messages when it reacts to the event.
karl. |
|
| Back to top |
|
|
MoeRadio.ru
Joined: 28 Jan 2007
Posts: 12
Location: Moscow, Russia
|
| Posted: Wed Dec 24, 2008 3:53 am Post subject: |
|
|
It doesn't seem to update error.log or any other log-file when I issue kill -HUP command.
What loglevel is needed for such thing to get into error.log? I have <loglevel>3</loglevel>. |
|
| Back to top |
|
|
karlH
Code Warrior
Joined: 13 Jun 2005
Posts: 5476
Location: UK
|
| Posted: Wed Dec 24, 2008 4:58 pm Post subject: |
|
|
If the HUP signal is received you should see several messages, rechecking the mountpoints/relays, applying settings etc. Maybe it's a permission thing?
karl. |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
