Re: [systemd-devel] systemd hibernator generator does not function on default Fedora install

2016-04-21 Thread Chris Murphy
On Wed, Apr 20, 2016 at 3:14 AM, Lennart Poettering wrote: > On Tue, 19.04.16 22:47, Chris Murphy (li...@colorremedies.com) wrote: > >> In some ancient bug or lkml I'd read a kernel maintainer say that the >> hibernation image size isn't fixed, and might be less than RAM size >> but could be a lit

Re: [systemd-devel] systemd hibernator generator does not function on default Fedora install

2016-04-21 Thread Lennart Poettering
On Thu, 21.04.16 16:06, Michael Biebl (mbi...@gmail.com) wrote: > Hi Lennart > > 2016-04-21 12:11 GMT+02:00 Lennart Poettering : > > On Thu, 21.04.16 02:50, Michael Biebl (mbi...@gmail.com) wrote: > > > >> 2016-04-21 0:56 GMT+02:00 Michael Biebl : > >> On second thought, maybe not such a good ide

[systemd-devel] [networkd] [RFC] ProfileName match constraint and profile selection via networkctl

2016-04-21 Thread Clemens Gruber
Hi, I have the following problem: I use systemd-networkd on an embedded ARM board but we have several different network usecases (with or without VLAN trunking, etc.) which need to be configurable. Until now, I tried to create a KernelCommandLine Match constraint to control which .network and .ne

Re: [systemd-devel] systemd hibernator generator does not function on default Fedora install

2016-04-21 Thread poma
On 19.04.2016 12:31, Harald Hoyer wrote: > > Here are my thought as the main dracut maintainer: > > To resume from a swap disk means, that you must not change any data on disk > while doing so, because that change would go unnoticed by the kernel, which we > want to resume. So basically assemblin

Re: [systemd-devel] systemd hibernator generator does not function on default Fedora install

2016-04-21 Thread Michael Biebl
2016-04-21 16:06 GMT+02:00 Michael Biebl : > Hi Lennart > > 2016-04-21 12:11 GMT+02:00 Lennart Poettering : >> On Thu, 21.04.16 02:50, Michael Biebl (mbi...@gmail.com) wrote: >> >>> 2016-04-21 0:56 GMT+02:00 Michael Biebl : >>> On second thought, maybe not such a good idea as this would break >>> h

Re: [systemd-devel] systemd hibernator generator does not function on default Fedora install

2016-04-21 Thread Michael Biebl
Hi Lennart 2016-04-21 12:11 GMT+02:00 Lennart Poettering : > On Thu, 21.04.16 02:50, Michael Biebl (mbi...@gmail.com) wrote: > >> 2016-04-21 0:56 GMT+02:00 Michael Biebl : >> On second thought, maybe not such a good idea as this would break >> hibernate on alternate initramfs generators, like init

Re: [systemd-devel] systemd hibernator generator does not function on default Fedora install

2016-04-21 Thread Harald Hoyer
On 20.04.2016 06:47, Chris Murphy wrote: > On Tue, Apr 19, 2016 at 4:10 AM, Lennart Poettering > wrote: > >> >> So what precisely are you proposing? That we actively search for the >> swap partition in the hibernate-resume generator? > > I think the main thing James is after, I know I'm in this

Re: [systemd-devel] systemd hibernator generator does not function on default Fedora install

2016-04-21 Thread Lennart Poettering
On Thu, 21.04.16 02:50, Michael Biebl (mbi...@gmail.com) wrote: > 2016-04-21 0:56 GMT+02:00 Michael Biebl : > > 2016-04-20 11:14 GMT+02:00 Lennart Poettering : > >> > >> Here's the heuristics code logind uses to check whether hibernation > >> shall be considered available or not: > >> > >> https:/

Re: [systemd-devel] Fwd: Stopping a service at a specific time or after a specific duration

2016-04-21 Thread Jamie Kitson
> >>> > >>> For stopping after a duration you can use RuntimeMaxSec=, introduced in > >>> v229. > >> > >> > >> Thanks. The man page says: > >> > >>> If this is used and the service has been active for longer than the > >>> specified > >>> time it is terminated and put into a failure state > > >

Re: [systemd-devel] Fwd: Stopping a service at a specific time or after a specific duration

2016-04-21 Thread Andrei Borzenkov
On Thu, Apr 21, 2016 at 11:32 AM, Reindl Harald wrote: > > > Am 20.04.2016 um 17:29 schrieb Jamie Kitson: >>> >>> For stopping after a duration you can use RuntimeMaxSec=, introduced in >>> v229. >> >> >> Thanks. The man page says: >> >>> If this is used and the service has been active for lon

Re: [systemd-devel] Fwd: Stopping a service at a specific time or after a specific duration

2016-04-21 Thread Reindl Harald
Am 20.04.2016 um 17:29 schrieb Jamie Kitson: For stopping after a duration you can use RuntimeMaxSec=, introduced in v229. Thanks. The man page says: If this is used and the service has been active for longer than the specified time it is terminated and put into a failure state and i