Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #268829

Re: inconsistency in the symlinks under /etc/systemd

Show all headers | View raw

On Thu 11 Apr 2024 at 19:28:48 (+0200), Vincent Lefevre wrote:
> On 2024-04-10 23:47:36 -0500, David Wright wrote:
> > On Thu 11 Apr 2024 at 03:36:59 (+0200), Vincent Lefevre wrote:
> > > On 2024-04-10 09:52:51 -0400, Dan Purgert wrote:
> > > > I'd hazard it's a consequence of usrmerge being the "default state" in
> > > > one installation and not the other.
> > > 
> > > Both machines have always been usr-merged (i.e. from the Debian
> > > installation).
> > 
> > This is trixie, is it not, so perhaps bugs are being fixed
> > in package installation support programs. You should be able
> > to see the symlinks being created in /var/log/apt/term.log*
> > if they haven't yet rotated away.
> 
> On the first machine:
> 
> Setting up dmeventd (2:1.02.185-2) ...
> Created symlink /etc/systemd/system/sockets.target.wants/dm-event.socket → /lib/systemd/system/dm-event.socket.
> Setting up lvm2 (2.03.16-2) ...
> Created symlink /etc/systemd/system/sysinit.target.wants/blk-availability.service → /lib/systemd/system/blk-availability.service.
> Created symlink /etc/systemd/system/sysinit.target.wants/lvm2-monitor.service → /lib/systemd/system/lvm2-monitor.service.
> Created symlink /etc/systemd/system/sysinit.target.wants/lvm2-lvmpolld.socket → /lib/systemd/system/lvm2-lvmpolld.socket.
> 
> On the second machine:
> 
> Setting up dmeventd (2:1.02.185-2) ...
> Created symlink /etc/systemd/system/sockets.target.wants/dm-event.socket → /usr/lib/systemd/system/dm-event.socket.
> Setting up lvm2 (2.03.16-2) ...
> Created symlink /etc/systemd/system/sysinit.target.wants/blk-availability.service → /usr/lib/systemd/system/blk-availability.service.
> Created symlink /etc/systemd/system/sysinit.target.wants/lvm2-monitor.service → /usr/lib/systemd/system/lvm2-monitor.service.
> Created symlink /etc/systemd/system/sysinit.target.wants/lvm2-lvmpolld.socket → /usr/lib/systemd/system/lvm2-lvmpolld.socket.
> 
> > Or else, have you run systemctl on dmeventd, in order to change its
> > status?
> 
> I'm not sure what to do.

I don't know anything about your machine, or the service provided by
these symlinks. But my own experience is that systemd is not bothered
about which of the two paths is the target, and renaming links with
ln -sf   doesn't affect running instances.

But for easing the task of comparing configurations, you could just
massage your listings so that any symlink targets listed as /lib…
appear as /usr/lib….

Cheers,
David.

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

inconsistency in the symlinks under /etc/systemd Vincent Lefevre <vincent@vinc17.net> - 2024-04-10 13:10 +0200
  Re: inconsistency in the symlinks under /etc/systemd Dan Purgert <dan@djph.net> - 2024-04-10 16:20 +0200
    Re: inconsistency in the symlinks under /etc/systemd Vincent Lefevre <vincent@vinc17.net> - 2024-04-11 04:10 +0200
      Re: inconsistency in the symlinks under /etc/systemd Vincent Lefevre <vincent@vinc17.net> - 2024-04-11 19:50 +0200
        Re: inconsistency in the symlinks under /etc/systemd David Wright <deblis@lionunicorn.co.uk> - 2024-04-12 21:10 +0200
      Re: inconsistency in the symlinks under /etc/systemd David Wright <deblis@lionunicorn.co.uk> - 2024-04-11 07:10 +0200
  Re: inconsistency in the symlinks under /etc/systemd David Wright <deblis@lionunicorn.co.uk> - 2024-04-10 16:30 +0200
  Re: inconsistency in the symlinks under /etc/systemd Jeffrey Walton <noloader@gmail.com> - 2024-04-10 21:00 +0200
    Re: inconsistency in the symlinks under /etc/systemd David Wright <deblis@lionunicorn.co.uk> - 2024-04-12 21:10 +0200

csiph-web