| 1 |
Alexey Mishustin wrote: |
| 2 |
>> So, restarting syslog-ng should be all that's required to fix it - reboot is |
| 3 |
>> >overkill. |
| 4 |
|
| 5 |
> As for me, first I updated syslog-ng, then I issued |
| 6 |
> '/etc/init.d/syslog-ng reload' (by mistake, instead of 'restart'), and |
| 7 |
> then 'restart' as I should. Then, just when syslog-ng was restarting, |
| 8 |
> the segfault happened. |
| 9 |
|
| 10 |
I also noted that restarting syslog didn't seem to solve the problem. I |
| 11 |
do think Adam's reasoning makes sense, but there must be something else |
| 12 |
that needed to be restarted as well. |
| 13 |
|
| 14 |
-- |
| 15 |
R |
Archives