News for hackers. Stuff that matters.
Re:NGINX syslog-ing without breaking the bank or patching th... by semiquaver on Tuesday November 26, 2013 @01:06PM (#6802971)
This seems dangerous -- if rsyslog crashes then the pipe is left without a consumer and all writes to it block indefinitely, exactly the opposite of how you would expect syslog to work.
Re:NGINX syslog-ing without breaking the bank or patching th... by rodgerd on Tuesday November 26, 2013 @01:35PM (#6803188)
If you were using systemd, I'd imagine you'd tell it to restart your syslogger automagically, and use ExecStartPost or ExecReload to tickle nginx.
Re:NGINX syslog-ing without breaking the bank or patching th... by nasalgoat on Tuesday November 26, 2013 @03:10PM (#6803840)
I'm a little concerned that these days to go-to answer for a crashing daemon is to have another daemon that watches it and restarts it.

Who watches the watchers? What happened to writing things that don't break?

Re:NGINX syslog-ing without breaking the bank or patching th... by nmcfarl on Tuesday November 26, 2013 @03:41PM (#6804051)
Whenever I hear this complaint the first thing I think about is this Douglas Adams quote:

  The major difference between a thing that might go wrong 
  and a thing that cannot possibly go wrong is that when a 
  thing that cannot possibly go wrong goes wrong it usually 
  turns out to be impossible to get at or repair.
Personally when doing operations related stuff I like to assume that everything will eventually break - though, hopefully not all at once.
Re:NGINX syslog-ing without breaking the bank or patching th... by asdasf on Tuesday November 26, 2013 @05:13PM (#6804644)
That quote is entirely inapplicable though. It is in fact much easier to fix the simple, do one thing and do it well unix style applications. They are not hard to get at or repair. This is one area where I think the linux philosophy winning out over the unix philosophy has really cost us a lot.
Re:NGINX syslog-ing without breaking the bank or patching th... by asdfaoeu on Tuesday November 26, 2013 @11:51PM (#6806479)
Re:NGINX syslog-ing without breaking the bank or patching th... by rodgerd on Tuesday November 26, 2013 @05:21PM (#6804699)
If your PID 1 is screwed, the ordering of syslogd/nginx restarts is the least of your worries.
Re:NGINX syslog-ing without breaking the bank or patching th... by otterley on Tuesday November 26, 2013 @03:04PM (#6803794)
Perhaps, but there are plenty of scenarios where restarting won't help (e.g. daemon misconfiguration).
Re:NGINX syslog-ing without breaking the bank or patching th... by pionar on Tuesday November 26, 2013 @03:12PM (#6803855)
Yes, and it will still hang in the amount of time it takes to restart rsyslog.
Re:NGINX syslog-ing without breaking the bank or patching th... by icebraining on Tuesday November 26, 2013 @01:25PM (#6803103)
You can just send an USR1 signal to nginx when you restart rsyslog (hopefully with some kind of supervisor). With Upstart, you could use a post-start script in the rsyslog service configuration.