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


Groups > linux.debian.user > #206089

Re: systemd error

From Reco <recoverym4n@enotuniq.net>
Newsgroups linux.debian.user
Subject Re: systemd error
Date 2019-03-10 08:40 +0100
Message-ID <xA1dT-7Rx-1@gated-at.bofh.it> (permalink)
References <xzv4l-4nc-1@gated-at.bofh.it> <xzEU2-26B-7@gated-at.bofh.it> <xzWHf-4St-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


	Hi.

On Sat, Mar 09, 2019 at 09:27:35PM -0500, Default User wrote:
> On Sat, Mar 9, 2019 at 2:45 AM Reco <recoverym4n@enotuniq.net> wrote:
> >
> > On Fri, Mar 08, 2019 at 04:00:05PM -0500, Default User wrote:
> > > Hi.  Got a (minor) systemd problem.
> > ...
> > >            └─3684 /usr/sbin/minissdpd -i enp7s0 -i wlp6s0
> > ...
> > > So, although the minissdpd.service unit is enables, it does not start
> > > automatically at boot, but will start manually using systemctl
> > start/stop.
> >
> > What is most likely happening at boot is that systemd tries to start
> > minissdpd before configuring interfaces enp7s0 and wlp6s0.
> > So it fails at boot, but works for manual restart because by then you
> > have both enp7s0 and wlp6s0 up and running.
> > Adding a dependency in the form of:
> >
> > [Unit]
> > After=sys-subsystem-net-devices-enp7s0.device
> > sys-subsystem-net-devices-wlp6s0.device
> > Requires=sys-subsystem-net-devices-enp7s0.device
> > sys-subsystem-net-devices-wlp6s0.device
> 
> Hi, Reco.
> Thanks for the reply and information.
> 
> Since I know very little about systemd, may I ask, should:
> 
> [Unit]
> After=sys-subsystem-net-devices-enp7s0.device
> sys-subsystem-net-devices-wlp6s0.device
> Requires=sys-subsystem-net-devices-enp7s0.device
> sys-subsystem-net-devices-wlp6s0.device
> 
> be appended to an existing .service or .target file, or should a new
> .service or .target file be created with these contents? And if a new file
> is needed, what should it be named, and in what directory should it be
> placed?

To do it proper systemd way, you should do the following:

# directory name is crucial
mkdir /etc/systemd/system/minissdpd.service.d
# file name is not important
cat > /etc/systemd/system/minissdpd.service.d/override.conf << EOF
[Unit]
After=sys-subsystem-net-devices-enp7s0.device sys-subsystem-net-devices-wlp6s0.device
Requires=sys-subsystem-net-devices-enp7s0.device sys-subsystem-net-devices-wlp6s0.device
EOF

systemctl daemon-reload

Just to be free of the formatting errors, you should create one directory,
and add three lines to one file inside it.

Reco

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


Thread

systemd error Default User <hunguponcontent@gmail.com> - 2019-03-08 22:20 +0100
  Re: systemd error Reco <recoverym4n@enotuniq.net> - 2019-03-09 08:50 +0100
    Re: systemd error Default User <hunguponcontent@gmail.com> - 2019-03-10 03:50 +0100
      Re: systemd error Reco <recoverym4n@enotuniq.net> - 2019-03-10 08:40 +0100
        Re: systemd error Eduardo M KALINOWSKI <eduardo@kalinowski.com.br> - 2019-03-10 12:10 +0100
          Re: systemd error Curt <curty@free.fr> - 2019-03-10 14:30 +0100
            Re: systemd error Reco <recoverym4n@enotuniq.net> - 2019-03-10 16:30 +0100
              Re: systemd error Curt <curty@free.fr> - 2019-03-10 17:50 +0100
              Re: systemd error Default User <hunguponcontent@gmail.com> - 2019-03-10 17:50 +0100
                Re: systemd error Default User <hunguponcontent@gmail.com> - 2019-03-10 20:50 +0100
                Re: systemd error Reco <recoverym4n@enotuniq.net> - 2019-03-10 21:10 +0100
                Re: systemd error Default User <hunguponcontent@gmail.com> - 2019-03-11 05:00 +0100
                Re: systemd error Sven Hartge <sven@svenhartge.de> - 2019-03-11 08:50 +0100
                Re: systemd error Default User <hunguponcontent@gmail.com> - 2019-03-11 13:50 +0100
                Re: systemd error Default User <hunguponcontent@gmail.com> - 2019-03-13 06:00 +0100
                Re: systemd error Default User <hunguponcontent@gmail.com> - 2019-03-13 06:10 +0100
                Re: systemd error <tomas@tuxteam.de> - 2019-03-13 09:50 +0100
                Re: systemd error Default User <hunguponcontent@gmail.com> - 2019-03-13 14:30 +0100
                Re: systemd error Dan Ritter <dsr@randomstring.org> - 2019-03-13 16:10 +0100
                Re: systemd error Default User <hunguponcontent@gmail.com> - 2019-03-13 19:20 +0100
                Re: systemd error deloptes <deloptes@gmail.com> - 2019-03-13 21:30 +0100
                Re: systemd error <tomas@tuxteam.de> - 2019-03-13 22:00 +0100
  Re: systemd error Curt <curty@free.fr> - 2019-03-09 10:30 +0100
    Re: systemd error Default User <hunguponcontent@gmail.com> - 2019-03-10 03:40 +0100
      Re: systemd error Curt <curty@free.fr> - 2019-03-10 10:40 +0100
        Re: systemd error Cindy-Sue Causey <butterflybytes@gmail.com> - 2019-03-10 15:10 +0100

csiph-web