Bug#879191: /usr/lib/modprobe.d/systemd.conf ignored, should be in /lib/modprobe.d
Package: systemd Version: 235-2 Severity: normal Hi, /usr/lib/modprobe.d/systemd.conf gets ignored, at least on non-usrmerged systems. The file should be in /lib/modprobe.d, where already other files are placed. Moving the file gets it honored. Greeetings Marc -- Package-specific info: -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.13.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd depends on: ii adduser 3.116 ii libacl1 2.2.52-3+b1 ii libapparmor12.11.0-11 ii libaudit1 1:2.8.1-1 ii libblkid1 2.30.2-0.1 ii libc6 2.24-17 ii libcap2 1:2.25-1.1 ii libcryptsetup4 2:1.7.5-1 ii libgcrypt20 1.7.9-1 ii libgpg-error0 1.27-3 ii libidn111.33-2 ii libip4tc0 1.6.1-2+b1 ii libkmod224-1 ii liblz4-10.0~r131-2+b1 ii liblzma55.2.2-1.3 ii libmount1 2.30.2-0.1 ii libpam0g1.1.8-3.6 ii libseccomp2 2.3.1-2.1 ii libselinux1 2.7-2 ii libsystemd0 235-2 ii mount 2.30.2-0.1 ii procps 2:3.3.12-3 ii util-linux 2.30.2-0.1 Versions of packages systemd recommends: ii dbus1.11.20-1 ii libpam-systemd 235-2 Versions of packages systemd suggests: pn policykit-1 pn systemd-container Versions of packages systemd is related to: pn dracut ii initramfs-tools 0.130 ii udev 235-2 -- no debconf information ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#879191: /usr/lib/modprobe.d/systemd.conf ignored, should be in /lib/modprobe.d
Am 20.10.2017 um 10:38 schrieb Marc Haber: > Package: systemd > Version: 235-2 > Severity: normal > > > Hi, > > /usr/lib/modprobe.d/systemd.conf gets ignored, at least on non-usrmerged > systems. The file should be in /lib/modprobe.d, where already other > files are placed. Moving the file gets it honored. > That path is read by kmod. Given that kmod supports /usr/lib/modules-load.d and /lib/modules-load.d/ it would imho make sense if it also supported /usr/lib/modprobe.d besides /lib/modprobe.d Marco, thoughts? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#791944: /etc/init.d/sendsigs kills systemd-udevd upon shutdown, causing dmsetup to hang
On Monday 12 June 2017 13:37:13 Pali Rohár wrote:
> On Saturday 10 June 2017 22:44:31 Michael Biebl wrote:
> > Hi
> >
> > Am 10.06.2017 um 21:14 schrieb Pali Rohár:
> >
> > > PING. Do you need to test something more? Or is that patch enough?
> >
> > The patch seems to contain some left-over comments. Afaics it also
> > misses the changes to the maintainer scripts which make sure the
> > /etc/rc{0,6} symlinks are created on upgrades.
>
> Anyway, change with sendsigs.omit.d is tested and is working. Will you
> prepare correct update of udev package for Stretch release? I hope that
> testing new patch which just clean-up and remove comments is not needed.
Michael, if you are not going to do that, can you at least show how to
update maintainer scripts and exactly is needed? I can prepare change,
but I do not know what exactly is needed for that. Thanks!
--
Pali Rohár
pali.ro...@gmail.com
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#879191: /usr/lib/modprobe.d/systemd.conf ignored, should be in /lib/modprobe.d
Am 20.10.2017 um 12:54 schrieb Michael Biebl: > Am 20.10.2017 um 10:38 schrieb Marc Haber: >> Package: systemd >> Version: 235-2 >> Severity: normal >> >> >> Hi, >> >> /usr/lib/modprobe.d/systemd.conf gets ignored, at least on non-usrmerged >> systems. The file should be in /lib/modprobe.d, where already other >> files are placed. Moving the file gets it honored. >> > > That path is read by kmod. Given that kmod supports > /usr/lib/modules-load.d and /lib/modules-load.d/ it would imho make > sense if it also supported /usr/lib/modprobe.d besides /lib/modprobe.d > > Marco, thoughts? > > See https://anonscm.debian.org/cgit/users/md/kmod.git/tree/libkmod/libkmod.c#n63 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#879191: /usr/lib/modprobe.d/systemd.conf ignored, should be in /lib/modprobe.d
On Fri, Oct 20, 2017 at 12:54:38PM +0200, Michael Biebl wrote: > That path is read by kmod. Given that kmod supports > /usr/lib/modules-load.d and /lib/modules-load.d/ it would imho make > sense if it also supported /usr/lib/modprobe.d besides /lib/modprobe.d Should it be decided that /usr/lib/modprobe.d is a valid place, modprobe.d(5) should be adapted to document reality. Greetings Marc -- - Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421 ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#879191: /usr/lib/modprobe.d/systemd.conf ignored, should be in /lib/modprobe.d
Am 20.10.2017 um 13:00 schrieb Marc Haber: > On Fri, Oct 20, 2017 at 12:54:38PM +0200, Michael Biebl wrote: >> That path is read by kmod. Given that kmod supports >> /usr/lib/modules-load.d and /lib/modules-load.d/ it would imho make >> sense if it also supported /usr/lib/modprobe.d besides /lib/modprobe.d > > Should it be decided that /usr/lib/modprobe.d is a valid place, > modprobe.d(5) should be adapted to document reality. Nod. The initramfs-tools hooks would have to be updated as well. Let's see what Marco says. I've also CCed Lucas, upstream of kmod. His input would be very much appreciated as well. Lucas, you can find the complete bug report at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879191 Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#879191: /usr/lib/modprobe.d/systemd.conf ignored, should be in /lib/modprobe.d
Control: forwarded -1 https://github.com/systemd/systemd/pull/7149 Am 20.10.2017 um 10:38 schrieb Marc Haber: > /usr/lib/modprobe.d/systemd.conf gets ignored, at least on non-usrmerged > systems. The file should be in /lib/modprobe.d, where already other > files are placed. Moving the file gets it honored. > Filed upstream as https://github.com/systemd/systemd/pull/7149 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processed: Re: Bug#879191: /usr/lib/modprobe.d/systemd.conf ignored, should be in /lib/modprobe.d
Processing control commands: > forwarded -1 https://github.com/systemd/systemd/pull/7149 Bug #879191 [systemd] /usr/lib/modprobe.d/systemd.conf ignored, should be in /lib/modprobe.d Set Bug forwarded-to-address to 'https://github.com/systemd/systemd/pull/7149'. -- 879191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879191 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#879216: /lib/systemd/system/systemd-resolved.service:22: Executable path is not absolute: !!/lib/systemd/systemd-resolved
Package: systemd Version: 235-2 Severity: normal Something about the service configuration for systemd-resolved doesn't match what the service manager expects. What does it mean to start an executable path with "!!" ? 0 dkg@alice:~$ systemctl status systemd-resolved ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/lib/systemd/system/systemd-resolved.service; disabled; vendor preset: enabled) Drop-In: /lib/systemd/system/systemd-resolved.service.d └─resolvconf.conf Active: inactive (dead) Docs: man:systemd-resolved.service(8) https://www.freedesktop.org/wiki/Software/systemd/resolved https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients Tasks: 0 (limit: 4915) CGroup: /system.slice/systemd-resolved.service Oct 16 16:16:23 alice systemd[1]: /lib/systemd/system/systemd-resolved.service:22: Executable path is not absolute: !!/lib/systemd/systemd-resolved Oct 16 16:16:23 alice systemd[1]: /lib/systemd/system/systemd-resolved.service:22: Executable path is not absolute: !!/lib/systemd/systemd-resolved Oct 16 16:16:24 alice systemd[1]: /lib/systemd/system/systemd-resolved.service:22: Executable path is not absolute: !!/lib/systemd/systemd-resolved 3 dkg@alice:~$ systemctl cat systemd-resolved | grep ExecStart ExecStart=!!/lib/systemd/systemd-resolved ExecStartPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || echo "nameserver 127.0.0.53" | /sbin/resolvconf -a systemd-resolved' 0 dkg@alice:~$ -- Package-specific info: -- System Information: Debian Release: buster/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing'), (500, 'oldstable'), (200, 'unstable-debug'), (200, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd depends on: ii adduser 3.116 ii libacl1 2.2.52-3+b1 ii libapparmor12.11.0-11 ii libaudit1 1:2.7.8-1 ii libblkid1 2.30.2-0.1 ii libc6 2.24-17 ii libcap2 1:2.25-1.1 ii libcryptsetup4 2:1.7.5-1 ii libgcrypt20 1.7.9-1 ii libgpg-error0 1.27-3 ii libidn111.33-2 ii libip4tc0 1.6.1-2 ii libkmod224-1 ii liblz4-10.0~r131-2+b1 ii liblzma55.2.2-1.3 ii libmount1 2.30.2-0.1 ii libpam0g1.1.8-3.6 ii libseccomp2 2.3.1-2.1 ii libselinux1 2.7-2 ii libsystemd0 235-2 ii mount 2.30.2-0.1 ii procps 2:3.3.12-3 ii util-linux 2.30.2-0.1 Versions of packages systemd recommends: ii dbus1.11.20-1 ii libpam-systemd 235-2 Versions of packages systemd suggests: ii policykit-10.105-18 ii systemd-container 235-2 Versions of packages systemd is related to: ii dracut 045+132-1 pn initramfs-tools ii udev 235-2 -- no debconf information ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#878625: systemd: NIS users login takes longtime.
Control: reassign -1 nis Control: retitle -1 "nscd should be a Depends" * Michael Biebl [2017-10-16 11:27 +0200]: > Control: forwarded -1 https://github.com/systemd/systemd/issues/7074 > > Am 15.10.2017 um 10:55 schrieb Elimar Riesebieter: > > Package: systemd > > Version: 235-2 > > Severity: normal > > > > Login as a NIS user journalctl tells: > > > > systemd-logind[666]: do_ypcall: clnt_call: RPC: Unable to send; errno = > > Operation not permitted > > pam_systemd(login:session): Failed to create session: Connection timed out > > > > User is logged in after a while and there is no /run/user/UID > > > > Running 234-3 from testing runs just fine. > > > > Looks like https://github.com/systemd/systemd/issues/7074 Installed nscd as proposed from Poettering. All runs fine now. Elimar -- On the keyboard of life you have always to keep a finger at the escape key;-) signature.asc Description: PGP signature ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processed: Re: Bug#878625: systemd: NIS users login takes longtime.
Processing control commands: > reassign -1 nis Bug #878625 [systemd] systemd: NIS users login takes longtime. Bug reassigned from package 'systemd' to 'nis'. No longer marked as found in versions systemd/235-2. Ignoring request to alter fixed versions of bug #878625 to the same values previously set > retitle -1 "nscd should be a Depends" Bug #878625 [nis] systemd: NIS users login takes longtime. Changed Bug title to '"nscd should be a Depends"' from 'systemd: NIS users login takes longtime.'. -- 878625: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878625 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#879216: marked as done (/lib/systemd/system/systemd-resolved.service:22: Executable path is not absolute: !!/lib/systemd/systemd-resolved)
Your message dated Fri, 20 Oct 2017 18:58:30 +0200 with message-id and subject line Re: /lib/systemd/system/systemd-resolved.service:22: Executable path is not absolute: !!/lib/systemd/systemd-resolved has caused the Debian Bug report #879216, regarding /lib/systemd/system/systemd-resolved.service:22: Executable path is not absolute: !!/lib/systemd/systemd-resolved to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 879216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879216 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd Version: 235-2 Severity: normal Something about the service configuration for systemd-resolved doesn't match what the service manager expects. What does it mean to start an executable path with "!!" ? 0 dkg@alice:~$ systemctl status systemd-resolved ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/lib/systemd/system/systemd-resolved.service; disabled; vendor preset: enabled) Drop-In: /lib/systemd/system/systemd-resolved.service.d └─resolvconf.conf Active: inactive (dead) Docs: man:systemd-resolved.service(8) https://www.freedesktop.org/wiki/Software/systemd/resolved https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients Tasks: 0 (limit: 4915) CGroup: /system.slice/systemd-resolved.service Oct 16 16:16:23 alice systemd[1]: /lib/systemd/system/systemd-resolved.service:22: Executable path is not absolute: !!/lib/systemd/systemd-resolved Oct 16 16:16:23 alice systemd[1]: /lib/systemd/system/systemd-resolved.service:22: Executable path is not absolute: !!/lib/systemd/systemd-resolved Oct 16 16:16:24 alice systemd[1]: /lib/systemd/system/systemd-resolved.service:22: Executable path is not absolute: !!/lib/systemd/systemd-resolved 3 dkg@alice:~$ systemctl cat systemd-resolved | grep ExecStart ExecStart=!!/lib/systemd/systemd-resolved ExecStartPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || echo "nameserver 127.0.0.53" | /sbin/resolvconf -a systemd-resolved' 0 dkg@alice:~$ -- Package-specific info: -- System Information: Debian Release: buster/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing'), (500, 'oldstable'), (200, 'unstable-debug'), (200, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd depends on: ii adduser 3.116 ii libacl1 2.2.52-3+b1 ii libapparmor12.11.0-11 ii libaudit1 1:2.7.8-1 ii libblkid1 2.30.2-0.1 ii libc6 2.24-17 ii libcap2 1:2.25-1.1 ii libcryptsetup4 2:1.7.5-1 ii libgcrypt20 1.7.9-1 ii libgpg-error0 1.27-3 ii libidn111.33-2 ii libip4tc0 1.6.1-2 ii libkmod224-1 ii liblz4-10.0~r131-2+b1 ii liblzma55.2.2-1.3 ii libmount1 2.30.2-0.1 ii libpam0g1.1.8-3.6 ii libseccomp2 2.3.1-2.1 ii libselinux1 2.7-2 ii libsystemd0 235-2 ii mount 2.30.2-0.1 ii procps 2:3.3.12-3 ii util-linux 2.30.2-0.1 Versions of packages systemd recommends: ii dbus1.11.20-1 ii libpam-systemd 235-2 Versions of packages systemd suggests: ii policykit-10.105-18 ii systemd-container 235-2 Versions of packages systemd is related to: ii dracut 045+132-1 pn initramfs-tools ii udev 235-2 -- no debconf information --- End Message --- --- Begin Message --- On Fri, 20 Oct 2017 11:24:04 -0400 Daniel Kahn Gillmor wrote: > Package: systemd > Version: 235-2 > Severity: normal > > Something about the service configuration for systemd-resolved doesn't > match what the service manager expects. What does it mean to start an > executable path with "!!" ? > That's a temporary issue. "!!" is documented at https://www.freedesktop.org/software/systemd/man/systemd.service.html#ExecStart= and new in v235. What happened is, that the new service file was install, something triggered daemon-reload, so v234 picked up the new service file file and complained about it as it didn't understand the syntax. Since we reexec systemd after a successful upgrade, this is just a cosmetic issue and I don
GREAT NEWS!!! – LOGO DESIGN PROFESSIONAL IS HERE FOR YOU (IN)
Hello there, It is with great pleasure to announce to you that your worries on getting the perfect logo for your businesses or websites are no more. Yes! And I am very sure you won’t want to miss out this great opportunity. With our years of experience in this field, we have been able to design logos for our clients based on their specifications and this will define the type of business they are into. We have worked on logos, design and development of websites for our clients in the past and they are always satisfied with the outcome. Below are the services we offer and their prices; Designing of logos at $75. Designing of websites at $299 Article and content writing at $10 and above SEO services, starting from $149. We value our clients more than anything and the success of our clients’ business is our main priority; for this reason, we don’t hesitate to deliver the quality and best services that they need to move their business forward. Among the numerous logos that we’ve designed for our clients in the past are shown below. Take your time to examine their coolness and awesomeness. This is a magnificent offer for you, I will say. As such, for you to enjoy these rambunctious and efficient opportunity, all you have to do is reply this message by emailing us and we will be delighted to serve you. Hurry now!!! This is the change for you to get your dream logo.Regards,Teresa Cook ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Toronto PO# 8730 + 8731
Hi, Please find attached Toronto PO# 8730 + 8731. Kindly forward the Proforma�s for confirmation. Please Click to Download We need these dispatched in the last week of This Month. Thanks, Bruce Bradley Download PO# 8730 + 8731.PDF 186K ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
