❦ 2 juillet 2015 16:49 +0200, Vincent Bernat <ber...@debian.org> :
>> When haproxy is installed, it adds a file:
>>
>> /etc/rsyslog.d/49-haproxy.conf
>>
>> This file configures:
>> * A log socket in the HAProxy chroot
>> * A separate log file for HAProxy log messages.
>>
>> However, after this file is installed, rsyslog is not restarted. The
>> result is that the log configuration doesn't work until the user
>> discovers this and manually restarts rsyslog.
>>
>> It would be nice if this could be done during package
>> installation. Maybe something like this in `haproxy.postinst` would
>> work?
>>
>> if [ -x '/etc/init.d/rsyslog' ]; then
>> invoke-rc.d rsyslog restart
>> fi
>
> I agree that we should signal to rsyslog that there is a new
> file. However, are we allowed to restart an "unrelated" service?
I have pointed to the fact that rsyslog may also have an upgrade running
and therefore stopped and restart would start it again and the start
operation would fail.
I am afraid that triggering a restart from another postinst script will
just pile up additional bugs.
--
Clothes make the man. Naked people have little or no influence on society.
-- Mark Twain
signature.asc
Description: PGP signature
