Reopen logfiles on SIGHUP or some other signal

Details

  • Type: Improvement Improvement
  • Status: Open Open
  • Priority: Minor Minor
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: Chef Client, Chef Server, Chef Solo, WebUI
  • Labels:
    None

Description

It would be nice if I wouldn't have to restart the daemons if I run logrotate (and avoid the thundering herd of chef-clients at 00:00 each day ).

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Gábor Vészi added a comment -

OK, I just found the copytruncate option of logrotate, so feel free to resolve the bug with WONTFIX.

Show
Gábor Vészi added a comment - OK, I just found the copytruncate option of logrotate, so feel free to resolve the bug with WONTFIX .
Hide
Permalink
KC Braunschweig added a comment -

No, copytruncate is not a solution, its a workaround. Daemons that gracefully reopen logfiles when signaled are the real solution, see nginx or unicorn for good examples.

Show
KC Braunschweig added a comment - No, copytruncate is not a solution, its a workaround. Daemons that gracefully reopen logfiles when signaled are the real solution, see nginx or unicorn for good examples.
Hide
Permalink
KC Braunschweig added a comment -

Haven't tried it yet, but looks like responding to a HUP was fixed in http://tickets.opscode.com/browse/CHEF-2491 . Can someone try it with logrotate and confirm?

Show
KC Braunschweig added a comment - Haven't tried it yet, but looks like responding to a HUP was fixed in http://tickets.opscode.com/browse/CHEF-2491 . Can someone try it with logrotate and confirm?

People

  • Assignee:
    Unassigned
    Reporter:
    Gábor Vészi
Vote (1)
Watch (2)

Dates

  • Created:
    Updated: