Hello.
Sorry if what I ask is very silly, but I feel I need to ask anyway...
If sysvinit started syslog and waited for it and then started
everything else, why can't we do the same with systemd?
I mean, don't create the socket and then start syslog, but just
start syslog and make
Le 25/09/2014 07:49, Michael Biebl a écrit :
> Am 25.09.2014 um 07:31 schrieb Raphaël HALIMI:
>> Le 24/09/2014 17:30, Michael Biebl a écrit :
>>> Am 24.09.2014 um 17:23 schrieb Raphaël HALIMI:
>
http://cgit.freedesktop.org/systemd/systemd/commit/?id=5e8b767df6e18444d5aff2987b5e5603361ed528
>>
Am 25.09.2014 um 07:31 schrieb Raphaël HALIMI:
> Le 24/09/2014 17:30, Michael Biebl a écrit :
>> Am 24.09.2014 um 17:23 schrieb Raphaël HALIMI:
>>> http://cgit.freedesktop.org/systemd/systemd/commit/?id=5e8b767df6e18444d5aff2987b5e5603361ed528
>>
>> Could you verify that this patch does indeed fix
Le 24/09/2014 17:30, Michael Biebl a écrit :
> Am 24.09.2014 um 17:23 schrieb Raphaël HALIMI:
>> Package: systemd
>> Version: 215-4
>> Severity: important
>> Tags: patch
>>
>> Playing around with journalctl, I stumbled upon some messages like this one:
>>
>> sept. 24 14:15:35 arche systemd-journal[
Am 24.09.2014 um 17:23 schrieb Raphaël HALIMI:
> Package: systemd
> Version: 215-4
> Severity: important
> Tags: patch
>
> Playing around with journalctl, I stumbled upon some messages like this one:
>
> sept. 24 14:15:35 arche systemd-journal[182]: Forwarding to syslog
> missed 9 messages.
>
>
Package: systemd
Version: 215-4
Severity: important
Tags: patch
Playing around with journalctl, I stumbled upon some messages like this one:
sept. 24 14:15:35 arche systemd-journal[182]: Forwarding to syslog
missed 9 messages.
A quick Google search brought up this thread on upstream mailing list
6 matches
Mail list logo
