Bug 398318 - Hudson is terminated upon ALRM signal
Summary: Hudson is terminated upon ALRM signal
Status: ASSIGNED
Alias: None
Product: Hudson
Classification: Technology
Component: Core (show other bugs)
Version: 3.0.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Winston Prakash CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-16 12:47 EST by Sven Kirmess CLA
Modified: 2013-01-17 06:05 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sven Kirmess CLA 2013-01-16 12:47:55 EST 
With Hudson 2.2.1 you could use the ALRM signal to tell Hudson to reopen the log file. We used that in our log rotation script that rotated the hudson log file every midnight.

With Hudson 3.0.0 a

$ kill -ALRM <pid of hudson>

results in a "Alarm clock" output on stdout and Hudson is immediately shut down.

Could be related with
https://bugs.eclipse.org/bugs/show_bug.cgi?id=398313
Comment 1 Winston Prakash CLA 2013-01-16 14:29:41 EST 
As you pointed out, I believe this bug is related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=398313

When we switch to Jetty Server from Winstone server for the bundled server, I guess we lost the ability to use kill -ALRM <pid of hudson>

I will find if it is possible to do the same for Jetty Server also.
Comment 2 Sven Kirmess CLA 2013-01-17 06:05:51 EST 
It doesn't have to be the ALRM signal but there should be a way to rotate log files without restarting Hudson because Hudson logs can get quite big. :)