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

2016-05-17 Thread James Hogarth
On 15 May 2016 at 08:11, James Hogarth wrote: > > On 15 May 2016 06:32, "Andrei Borzenkov" wrote: > > > > 15.05.2016 06:36, Chris Murphy пишет: > > > On Thu, May 12, 2016 at 12:38 PM, James Hogarth < > james.hoga...@gmail.com> wrote: > > &

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

2016-05-15 Thread James Hogarth
On 15 May 2016 06:32, "Andrei Borzenkov" wrote: > > 15.05.2016 06:36, Chris Murphy пишет: > > On Thu, May 12, 2016 at 12:38 PM, James Hogarth wrote: > >> > >> On 2 May 2016 18:58, "James Hogarth" wrote: > >>> > >>> &g

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

2016-05-12 Thread James Hogarth
On 2 May 2016 18:58, "James Hogarth" wrote: > > > On 24 Apr 2016 21:31, "poma" wrote: > > > > On 20.04.2016 22:42, Chris Murphy wrote: > > > On Wed, Apr 20, 2016 at 1:50 PM, Tobias Hunger < tobias.hun...@gmail.com> wrote: > > > &g

Re: [systemd-devel] when/where was support for assigning "ethX" names removed?

2016-05-12 Thread James Hogarth
> > On 12 May 2016 18:28, "Chris Friesen" wrote: > > > > Hi, > > > > Could someone point me to the commit that removed support for assigning "ethX" names based on MAC addresses? > > > > Alternately, can someone suggest a way to get equivalent behaviour (the ability to set "ethX" names based on MAC

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

2016-05-02 Thread James Hogarth
On 24 Apr 2016 21:31, "poma" wrote: > > On 20.04.2016 22:42, Chris Murphy wrote: > > On Wed, Apr 20, 2016 at 1:50 PM, Tobias Hunger wrote: > > [...] > > > Anyway, the most complete solution for BIOS, UEFI, and UEFI Secure > > Boot systems, is fast startups as possible (which helps all kinds of >

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

2016-04-20 Thread James Hogarth
On 20 April 2016 at 10:20, Lennart Poettering wrote: > On Wed, 20.04.16 08:00, James Hogarth (james.hoga...@gmail.com) wrote: > > > Regardless of how the hibernate generator might potentially be changed to > > attempt to locate a valid swap partition with hibernate data, or

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

2016-04-20 Thread James Hogarth
On 20 Apr 2016 05: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 i

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

2016-04-19 Thread James Hogarth
On 19 Apr 2016 08:05, "Andrei Borzenkov" wrote: > > On Tue, Apr 19, 2016 at 9:45 AM, James Hogarth wrote: > > > > > Seeing as systemd decides the swap to hibernate to in the first place, can't > > No, it does not. Device to hibernate to is set by prev

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

2016-04-18 Thread James Hogarth
On 19 Apr 2016 04:53, "Andrei Borzenkov" wrote: > > 19.04.2016 01:19, James Hogarth пишет: > > Hi all, > > > > There's been some discussion today about the impact of > > https://bugzilla.redhat.com/show_bug.cgi?id=1206936 and where the prob

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

2016-04-18 Thread James Hogarth
Hi all, There's been some discussion today about the impact of https://bugzilla.redhat.com/show_bug.cgi?id=1206936 and where the problem actually lies. The issue lies specifically with hibernate and affects all Fedora systems regardless of hardware (it's reproducible in a VM). The hibernate imag

Re: [systemd-devel] socket activated services and correct dependency mapping

2015-07-25 Thread James Hogarth
On 24 Jul 2015 11:55, "Dimitri John Ledkov" wrote: > > On 24 July 2015 at 10:38, James Hogarth wrote: > > I want a user to be able to systemctl start sslh and use listening > > addresses in /etc/sslh.cfg as always (so I'm reluctant to put a > > straight So

Re: [systemd-devel] socket activated services and correct dependency mapping

2015-07-24 Thread James Hogarth
On 24 July 2015 at 10:38, James Hogarth wrote: > Hi, > > I'm in the process of adding systemd native sockets to a service > (rather than using inetd compatibility) and am trying to get my head > around the proper way to configure the unit files so that the socket >

[systemd-devel] socket activated services and correct dependency mapping

2015-07-24 Thread James Hogarth
Hi, I'm in the process of adding systemd native sockets to a service (rather than using inetd compatibility) and am trying to get my head around the proper way to configure the unit files so that the socket is optional rather than required but allowing restarting of the socket unit. https://githu

Re: [systemd-devel] Possible systemd segfault switching from 216 to 219 in fedora upgrade

2015-03-09 Thread James Hogarth
On 8 March 2015 at 22:32, Lennart Poettering wrote: > On Thu, 05.03.15 22:07, James Hogarth (james.hoga...@gmail.com) wrote: > >> > Tried to put together a reduced testcase via a yum installroot style >> > container to switch-root into to see what that behaviour is like an

Re: [systemd-devel] Possible systemd segfault switching from 216 to 219 in fedora upgrade

2015-03-05 Thread James Hogarth
On 5 March 2015 at 17:07, James Hogarth wrote: > On 5 March 2015 at 15:10, Lennart Poettering wrote: >> >> >> Right before switch rooting systemd will kill all remaining processes >> of the initrd, including the strace, hence the strace logs aren't that >&

Re: [systemd-devel] Possible systemd segfault switching from 216 to 219 in fedora upgrade

2015-03-05 Thread James Hogarth
On 5 March 2015 at 15:10, Lennart Poettering wrote: > > > Right before switch rooting systemd will kill all remaining processes > of the initrd, including the strace, hence the strace logs aren't that > useful either, they end before the transition. > > Please boot with "systemd.log_level=debug sy

[systemd-devel] Possible systemd segfault switching from 216 to 219 in fedora upgrade

2015-03-05 Thread James Hogarth
Hi, I spent some time last night trying to track down the issue preventing fedup from fedora 21 to 22: https://bugzilla.redhat.org/show_bug.cgi?id=1185604 I'm pretty sure I've tracked it down to when switch-root is called and systemd-219 gets executed being passed the serialised state of systemd