Re: [systemd-devel] Utility for persistent alternative driver binding

On 12/06/2015 08:56 AM, Andrei Borzenkov wrote: 04.12.2015 12:40, Panu Matilainen пишет: Hi all, To follow-up on this thread from September-October: http://lists.freedesktop.org/archives/systemd-devel/2015-September/034427.html

Re: [systemd-devel] Utility for persistent alternative driver binding

On 12/04/2015 04:41 PM, poma wrote: On 04.12.2015 15:27, poma wrote: On 04.12.2015 10:40, Panu Matilainen wrote: Hi all, To follow-up on this thread from September-October: http://lists.freedesktop.org/archives/systemd-devel/2015-September/034427.html

[systemd-devel] systemd shutdown: switch-root after remounting root fs ro

Hi, I am new to systemd. I am currently running Ubuntu 15.04 with ZFS. I would like to switch root filesystem to a tmpfs during system shutdown to reset root ZFS mount point (to dual boot FreeBSD). I have used /lib/systemd/system-shutdown/foo script. I have tried using systemctl switch-root,

Re: [systemd-devel] Github issue progress stalled

On 08.12.2015 11:57, Colin Guthrie wrote: > > There also seems to be no way to remove a "needs-reporter-feedback" tag > after I've provided feedback so it'll probably be getting ignored in any > workflows you use that exclude bugs with that tag. > > How is this workflow with GH issues supposed

Re: [systemd-devel] systemd shutdown: switch-root after remounting root fs ro

On Dec 8, 2015 12:13, "Radoslaw Kamil Ejsmont" wrote: > > Hi, > > I am new to systemd. I am currently running Ubuntu 15.04 with ZFS. I would like to switch root filesystem to a tmpfs during system shutdown to reset root ZFS mount point (to dual boot FreeBSD). I have used

[systemd-devel] Github issue progress stalled

Hi, I've been trying to document my progress and give requested feedback on a rather major regression that's badly affecting my system. The issue seems to have stalled, and I'm receiving no further updates despite providing the requested details. https://github.com/systemd/systemd/issues/1579

Re: [systemd-devel] Utility for persistent alternative driver binding

On Tue, Dec 08, 2015 at 09:14:17AM -0500, Charles (Chas) Williams wrote: > On Tue, 2015-12-08 at 11:34 +0200, Panu Matilainen wrote: > > Hmm, got a pointer? I dont think PCI slots change between reboots > > without physically swapping hardware, the "ethX-problem" comes from the > > order of

Re: [systemd-devel] Utility for persistent alternative driver binding

On Tue, 2015-12-08 at 11:34 +0200, Panu Matilainen wrote: > Hmm, got a pointer? I dont think PCI slots change between reboots > without physically swapping hardware, the "ethX-problem" comes from the > order of device discovery being unstable across boots, which is a > different issue and not

Re: [systemd-devel] Utility for persistent alternative driver binding

On Tue, Dec 08, 2015 at 09:46:13AM -0500, Charles (Chas) Williams wrote: > On Tue, 2015-12-08 at 14:21 +, Daniel P. Berrange wrote: > > On Tue, Dec 08, 2015 at 09:14:17AM -0500, Charles (Chas) Williams wrote: > > > On Tue, 2015-12-08 at 11:34 +0200, Panu Matilainen wrote: > > > > Hmm, got a

Re: [systemd-devel] Utility for persistent alternative driver binding

On Tue, 2015-12-08 at 14:21 +, Daniel P. Berrange wrote: > On Tue, Dec 08, 2015 at 09:14:17AM -0500, Charles (Chas) Williams wrote: > > On Tue, 2015-12-08 at 11:34 +0200, Panu Matilainen wrote: > > > Hmm, got a pointer? I dont think PCI slots change between reboots > > > without physically

[systemd-devel] Systemd and ceph-osd start

Hi, I try to test ceph 9.2 cluster. My lab have 1 mon and 2 osd with 4 disks each. Only 1 osd server (with 4 disks) are online. The disks of second osd don't go up ... Some info about environment: [ceph@OSD1 ~]$ sudo ceph osd tree ID WEIGHT TYPE NAME UP/DOWN REWEIGHT

Re: [systemd-devel] Utility for persistent alternative driver binding

On Tue, Dec 08, 2015 at 11:34:36AM +0200, Panu Matilainen wrote: > >As was mentioned recently PCI bus numbers may change between reboots, so > > Hmm, got a pointer? I dont think PCI slots change between reboots without > physically swapping hardware, the "ethX-problem" comes from the order of >

Re: [systemd-devel] Additional error details when resource limits are exceeded

Hi, it turns out that the teamviewer daemon wasn't behaving correctly and double-forked before the PID file was written. Fixed by running it as Type=simple and in the foreground. It however, still doesn't change anything about the error message, which is just plain wrong in this case as

Re: [systemd-devel] Utility for persistent alternative driver binding

On 12/08/2015 01:47 PM, Greg KH wrote: On Tue, Dec 08, 2015 at 11:34:36AM +0200, Panu Matilainen wrote: As was mentioned recently PCI bus numbers may change between reboots, so Hmm, got a pointer? I dont think PCI slots change between reboots without physically swapping hardware, the

[systemd-devel] question about the conditions for bus_enter_closing()

Hi, All          In the sd-bus.c, there are four conditions for calling the bus_enter_closing, as is:                          if (r == -ENOTCONN || r == -ECONNRESET || r == -EPIPE || r == -ESHUTDOWN) {                                    bus_enter_closing(bus);