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

Groups > linux.debian.user > #206092

Re: systemd error

Show all headers | View raw

On 10/03/2019 04:20, Reco wrote:
> On Sat, Mar 09, 2019 at 09:27:35PM -0500, Default User wrote:
>> 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

Or run

systemctl edit minissdpd.service

which will create the file in the appropriate location, open $EDITOR on
it, and run daemon-reload automatically afterwards.


-- 
Everyone is a genius.  It's just that some people are too stupid to
realize it.

Eduardo M KALINOWSKI
eduardo@kalinowski.com.br

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