Re: nis: NIS is started before rpcbind since rpcbind was migrated to systemd

On Sat, Feb 06, 2016 at 12:47:47AM +0100, Michael Biebl wrote: > If you run "systemctl edit rpcbind.socket" and add the following: > > [Unit] > DefaultDependencies=no > Wants=rpcbind.target > Before=rpcbind.target > > Is the problem gone after a reboot? > If not, can you please attach the output of

Re: nis: NIS is started before rpcbind since rpcbind was migrated to systemd

On Fri, 22 Jan 2016 13:03:00 -0800 Nye Liu wrote: > For some reason, even though $portmap is mentioned in /etc/init.d/nis as a > start prereq, ypbind is started BEFORE rpcbind. > > This causes ypbind to NEVER properly start, and the bind_wait obviously cannot > ever succeed. > >> Jan 22 12:51:01

Bug#813847: dracut: create fsck flag files (like initramfs-tools)

Package: dracut Version: 044+3-3 Severity: wishlist Tags: patch On 02-02-2016 22:27, Michael Biebl wrote: > Regarding the flag files dracut generates for non-systemd mode: > Could you please file a bug report so it uses > /run/initramfs/fsck-root for / > and > /run/initramfs/fsck-usr for /usr > >

Bug#813789: systemd: su -l does not start/attach to user session

Am 02/05/2016 um 10:51 AM schrieb Boris Kolpackov: > Package: systemd > Version: 215-17+deb8u2 > Severity: normal > > Hi, > > I keep seeing in various places (Debian-related and otherwise) that > su does not start a new systemd user session because it is not a > proper login. The symptom is: > >

Bug#813789: systemd: su -l does not start/attach to user session

Michael Biebl writes: > Actually in Debian, su *does* start a logind session. If you look at > > /etc/pam.d/su it includes /etc/pam.d/common-session It does: # The standard Unix authentication modules, used with # NIS (man nsswitch) as well as normal /etc/passwd and # /etc/shadow entries. @inc

Bug#768450: marked as done (invoke-rc.d: will start a disabled service for systemd-only or systemd+upstart config)

Your message dated Fri, 05 Feb 2016 11:49:33 + with message-id and subject line Bug#768450: fixed in init-system-helpers 1.28 has caused the Debian Bug report #768450, regarding invoke-rc.d: will start a disabled service for systemd-only or systemd+upstart config to be marked as done. This m

Bug#760168: marked as done (dh-systemd: support for -X option)

Your message dated Fri, 05 Feb 2016 11:49:33 + with message-id and subject line Bug#760168: fixed in init-system-helpers 1.28 has caused the Debian Bug report #760168, regarding dh-systemd: support for -X option to be marked as done. This means that you claim that the problem has been dealt w

Bug#717109: marked as done (invoke-rc.d: Allow stop and status requests for masked systemd services)

Your message dated Fri, 05 Feb 2016 11:49:33 + with message-id and subject line Bug#717109: fixed in init-system-helpers 1.28 has caused the Debian Bug report #717109, regarding invoke-rc.d: Allow stop and status requests for masked systemd services to be marked as done. This means that you

Bug#747851: marked as done (invoke-rc.d: does not execute action if a package only has an upstart job and a systemd unit)

Your message dated Fri, 05 Feb 2016 11:49:33 + with message-id and subject line Bug#747851: fixed in init-system-helpers 1.28 has caused the Debian Bug report #747851, regarding invoke-rc.d: does not execute action if a package only has an upstart job and a systemd unit to be marked as done.

init-system-helpers_1.28_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 05 Feb 2016 12:30:53 +0100 Source: init-system-helpers Binary: init-system-helpers dh-systemd init Architecture: source all amd64 Version: 1.28 Distribution: unstable Urgency: medium Maintainer: pkg-systemd-maintai

Processing of init-system-helpers_1.28_amd64.changes

init-system-helpers_1.28_amd64.changes uploaded successfully to localhost along with the files: init-system-helpers_1.28.dsc init-system-helpers_1.28.tar.xz dh-systemd_1.28_all.deb init-system-helpers_1.28_all.deb init_1.28_amd64.deb Greetings, Your Debian queue daemon (running

Bug#813789: systemd: su -l does not start/attach to user session

Am 02/05/2016 um 10:51 AM schrieb Boris Kolpackov: > Package: systemd > Version: 215-17+deb8u2 > Severity: normal > > Hi, > > I keep seeing in various places (Debian-related and otherwise) that > su does not start a new systemd user session because it is not a > proper login. The symptom is: Act

Bug#813789: systemd: su -l does not start/attach to user session

Package: systemd Version: 215-17+deb8u2 Severity: normal Hi, I keep seeing in various places (Debian-related and otherwise) that su does not start a new systemd user session because it is not a proper login. The symptom is: # su -l boris $ systemctl --user status Failed to get D-Bus connection:

Bug#760848: systemd: cannot boot lvm on raid on lvm system anymore

Hi Vincent On Mon, 08 Sep 2014 15:29:02 +0200 Vincent Danjean wrote: > Package: systemd > Version: 214-1 > Severity: important > > Hi, > > Since I siwtch to systemd, I cannot boot my system anymore without typing > complex commands in rescue mode. > My system layout is complex as I'm usin