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

Groups > linux.debian.user > #206132

Re: systemd error

From Reco <recoverym4n@enotuniq.net>
Newsgroups linux.debian.user
Subject Re: systemd error
Date 2019-03-10 21:10 +0100
Message-ID <xAcVH-6XF-1@gated-at.bofh.it> (permalink)
References (5 earlier) <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> <xAcCm-6zX-3@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw

	Hi.

On Sun, Mar 10, 2019 at 03:30:46PM -0400, Default User wrote:
> 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!

That does not simplify things.
Some sections of systemd unit file are magic, you cannot override them
like this.
Time for plan B then.

Remove /etc/systemd/system/minissdpd.service.d/override.conf
Copy /lib/systemd/system/minissdpd.service to
/etc/systemd/system/minissdpd.service.
Edit the resulting file.

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