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

Groups > linux.debian.user > #206129

Re: systemd error

From Default User <hunguponcontent@gmail.com>
Newsgroups linux.debian.user
Subject Re: systemd error
Date 2019-03-10 20:50 +0100
Message-ID <xAcCm-6zX-3@gated-at.bofh.it> (permalink)
References (4 earlier) <xA4v7-1B9-3@gated-at.bofh.it> <xA6GC-2SY-13@gated-at.bofh.it> <xA8yK-46q-19@gated-at.bofh.it> <xA9Oa-4Nl-9@gated-at.bofh.it> <xAcCm-6zX-5@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On Sun, Mar 10, 2019 at 1:45 PM Eduardo M KALINOWSKI <
eduardo@kalinowski.com.br> wrote:

> On 10/03/2019 13:25, Default User wrote:
>
> So, should I try manually editing /lib/systemd/system/minissdpd.service?
>
> If you do that, you'll lose changes the next time the package is upgraded.
>
> To see if systemd is seeing your add-in file, use 'systemctl cat
> minissdpd.service'. It should list your file and it's contents.
>
>
> --
> Soldiers who wish to be a hero
> Are practically zero,
> But those who wish to be civilians,
> They run into the millions.
>
> Eduardo M KALINOWSKIeduardo@kalinowski.com.br
>
>

Well,

 doofus@doofus:~$ ls /lib/systemd/system/minissdpd.service
-rw-r--r-- 1 root root 418 Feb 27 22:13
/lib/systemd/system/minissdpd.service


doofus@doofus:~$ sudo cat /lib/systemd/system/minissdpd.service
[Unit]
Description=keep memory of all UPnP devices that announced themselves
Documentation=man:minissdpd(1)
After=network-online.target

[Service]
Type=forking
EnvironmentFile=/etc/default/minissdpd
ExecStart=/usr/lib/minissdpd/minissdpd-systemd-wrapper
${MiniSSDPd_INTERFACE_ADDRESS} $MiniSSDPd_OTHER_OPTIONS
PrivateTmp=yes
LimitNOFILE=20
LimitNPROC=5
PIDFile=/run/minissdpd.pid

[Install]
WantedBy=multi-user.target

----------
But . . .
----------

doofus@doofus:~$ systemctl cat minissdpd.service
# /lib/systemd/system/minissdpd.service
[Unit]
Description=keep memory of all UPnP devices that announced themselves
Documentation=man:minissdpd(1)
After=network-online.target

[Service]
Type=forking
EnvironmentFile=/etc/default/minissdpd
ExecStart=/usr/lib/minissdpd/minissdpd-systemd-wrapper
${MiniSSDPd_INTERFACE_ADDRESS} $MiniSSDPd_OTHER_O
PrivateTmp=yes
LimitNOFILE=20
LimitNPROC=5
PIDFile=/run/minissdpd.pid

[Install]
WantedBy=multi-user.target

# /etc/systemd/system/minissdpd.service.d/override.conf
[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

----------

So, the file  /lib/systemd/system/minissdpd.service is unchanged since Feb
27 22:13.  It does NOT appear to include the contents of, or even refer
to,  /etc/systemd/system/minissdpd.service.d/override.conf, dated Mar 10
11:23.

Yet systemctl cat minissdpd.service DOES appear to reference
/etc/systemd/system/minissdpd.service.d/override.conf!

???

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