On Wed, Oct 26, 2022 at 12:14 PM Michael Biebl wrote:
>
> Am 26.10.22 um 11:49 schrieb Jędrzej Dudkiewicz:
> > I'm sorry if it was answered earlier, but I *really* couldn't find
> > anything about it.
> >
> > I have few packages that are installed as part of a larger system on
> > Debian running
Am 26.10.22 um 12:14 schrieb Michael Biebl:
This trigger is activated by packages installing files into /etc/rsyslog.d
But you can activate that trigger explicitly as well via
dpkg-trigger --now-await rsyslog
So, if your package ships a file in /etc/rsyslog.d/ everything should
work ootb.
Am 26.10.22 um 11:53 schrieb julien.pu...@gmail.com:
Le mercredi 26 octobre 2022 à 11:49 +0200, Jędrzej Dudkiewicz a écrit :
in its postinstall script. As this causes rsyslog to be restarted a
few times in a row it sometimes results in rsyslog not functioning.
High-severity issue right
Am 26.10.22 um 11:49 schrieb Jędrzej Dudkiewicz:
I'm sorry if it was answered earlier, but I *really* couldn't find
anything about it.
I have few packages that are installed as part of a larger system on
Debian running on BeagleBone. These packages frequently (for some
strange reason - I'm not
Le mercredi 26 octobre 2022 à 11:49 +0200, Jędrzej Dudkiewicz a écrit :
>
> in its postinstall script. As this causes rsyslog to be restarted a
> few times in a row it sometimes results in rsyslog not functioning.
>
High-severity issue right there: restarting should just work no matter
what.
I'm sorry if it was answered earlier, but I *really* couldn't find
anything about it.
I have few packages that are installed as part of a larger system on
Debian running on BeagleBone. These packages frequently (for some
strange reason - I'm not the only developer) modify files that go to
the
6 matches
Mail list logo
