Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#1040458: bookworm: please document that /etc/init.d/rsyslog is gone
1 view
Skip to first unread message
g1
Jul 6, 2023, 4:20:04 AM7/6/23
to
Package: release-notes
Severity: wishlist
On servers that run sysvinit instead of systemd, after upgrading from
bullseye to bookworm rsyslogd doesn't start at boot anymore, unless
orphan-sysvinit-packages is installed.
Perhaps it's worth mentioning in the RN, otherwise people might discover
that logging was stopped days or weeks after the upgrade.
Best regards,
g.b.
Severity: wishlist
On servers that run sysvinit instead of systemd, after upgrading from
bullseye to bookworm rsyslogd doesn't start at boot anymore, unless
orphan-sysvinit-packages is installed.
Perhaps it's worth mentioning in the RN, otherwise people might discover
that logging was stopped days or weeks after the upgrade.
Best regards,
g.b.
Paul Gevers
Jul 6, 2023, 4:32:05 AM7/6/23
to
Hi,
On 06-07-2023 10:01, g1 wrote:
> On servers that run sysvinit instead of systemd, after upgrading from
> bullseye to bookworm rsyslogd doesn't start at boot anymore, unless
> orphan-sysvinit-packages is installed.
>
> Perhaps it's worth mentioning in the RN, otherwise people might discover
> that logging was stopped days or weeks after the upgrade.
So something along the lines of:
Hosts not running the default init system (systemd) should check if all
relevant services are restarted after the upgrade. Some packages have
stopped shipping their own init scripts, although many of them can be
brought back by installing orphan-sysvinit-packages.
Is that what you had in mind?
Paul
On 06-07-2023 10:01, g1 wrote:
> On servers that run sysvinit instead of systemd, after upgrading from
> bullseye to bookworm rsyslogd doesn't start at boot anymore, unless
> orphan-sysvinit-packages is installed.
>
> Perhaps it's worth mentioning in the RN, otherwise people might discover
> that logging was stopped days or weeks after the upgrade.
Hosts not running the default init system (systemd) should check if all
relevant services are restarted after the upgrade. Some packages have
stopped shipping their own init scripts, although many of them can be
brought back by installing orphan-sysvinit-packages.
Is that what you had in mind?
Paul
g1...@libero.it
Jul 6, 2023, 5:42:44 AM7/6/23
to
Hi,
On Thu, Jul 06, 2023 at 10:18:39AM +0200, Paul Gevers wrote:
> Hi,
Plus a sentence in section "5.1.7 - Changes to system logging", because
on a server running sysvinit most likely no rsyslogd means no logs at all.
Best,
g.b.
On Thu, Jul 06, 2023 at 10:18:39AM +0200, Paul Gevers wrote:
> Hi,
>
> So something along the lines of:
>
> Hosts not running the default init system (systemd) should check if all
> relevant services are restarted after the upgrade. Some packages have
> stopped shipping their own init scripts, although many of them can be
> brought back by installing orphan-sysvinit-packages.
>
> Is that what you had in mind?
>
> Paul
Yes, that.
> So something along the lines of:
>
> Hosts not running the default init system (systemd) should check if all
> relevant services are restarted after the upgrade. Some packages have
> stopped shipping their own init scripts, although many of them can be
> brought back by installing orphan-sysvinit-packages.
>
> Is that what you had in mind?
>
> Paul
Plus a sentence in section "5.1.7 - Changes to system logging", because
on a server running sysvinit most likely no rsyslogd means no logs at all.
Best,
g.b.
0 new messages