[systemd-devel] Impossible to add events to event loop without adding at least one event before calling sd_event_loop() on systemd 222

Hi, Just wondering if it should be possible to add events the empty event loop. Christian Lockley ___ systemd-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] Best way to ensure only registered clients can use certain methods.

Hi all, I developing an app that returns an id after and init function, this id is to be passed the subsequent calls so the program can prevent clients from modifying the internal state of other clients. Right now I store the value returned by sd_bus_message_get_sender() in the init function then

Re: [systemd-devel] why does bootctl default to /boot and not to /boot/efi?

On Sun, 29 May 2016, Barry Scott wrote: I just came across the bootctl command. Atleast on Fedora 23 and 24 it errors out because /boot is not FAT EFI. I thought that if you are EFI then the EFI was always in /boot/efi. Is there something I'm missing or is the default path wrong on Fedora? I d

Re: [systemd-devel] UEFI menu entries wiped from BIOS after power off at dm-crypt boot prompt

On Sat, May 21, 2016 at 2:43 PM, Jamie Kitson wrote: > Hi, > > if I power off my computer at the dm-crypt boot password prompt my UEFI > menu entries get wiped from the BIOS and reset to the single default > Windows option. > > This is with an Asus UX32VD laptop, Grub UEFI and systemd and sd-encry

Re: [systemd-devel] Systemd loads units before btrfs subvolumes are mounted

On Wed, May 25, 2016 at 9:21 AM, Lennart Poettering wrote: > What I don't understand in your case though is why you use an explicit > mount for /opt anyway... The nice thing about btrfs is that subvolumes > behave pretty much like normal directories that just have a bit more > features. And becau

Re: [systemd-devel] why does bootctl default to /boot and not to /boot/efi?

On Sun, May 29, 2016 at 12:39 PM, Barry Scott wrote: > I just came across the bootctl command. Atleast on Fedora 23 and 24 > it errors out because /boot is not FAT EFI. I thought that if you are EFI > then the EFI was always in /boot/efi. > > Is there something I'm missing or is the default path w

Re: [systemd-devel] Erlang bindings for systemd-notify API

On Sun, May 29, 2016 at 10:59:23AM +0200, Peter Lemenkov wrote: > Hello All! > I'd like to introduce another systemd-related project - > erlang-sd_notify. That's just a bindings for sd_notify API. Currently > it implements bindings just for two functions - sd_notify and > sd_notifyf, which is enoug

[systemd-devel] why does bootctl default to /boot and not to /boot/efi?

I just came across the bootctl command. Atleast on Fedora 23 and 24 it errors out because /boot is not FAT EFI. I thought that if you are EFI then the EFI was always in /boot/efi. Is there something I'm missing or is the default path wrong on Fedora? Barry ___

Re: [systemd-devel] shutdown delayed by failure to start a service

29.05.2016 20:28, Felix Miata пишет: > Lennart Poettering composed on 2016-05-29 18:40 (UTC+0200): > >> Felix Miata wrote: > >>> The message I see is equivalent in form as during boot, e.g. when a >>> filesystem not noauto in fstab is to be mounted but cannot be found, >>> so a >>> delay of typic

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

29.05.2016 19:55, Michael Biebl пишет: > 2016-05-29 18:28 GMT+02:00 Lennart Poettering : >> On Sat, 28.05.16 21:38, Martin Pitt ([email protected]) wrote: >> >>> Chris Friesen [2016-05-27 9:14 -0600]: The reason why I'm poking at this is that the old scheme worked "good enough" for

Re: [systemd-devel] shutdown delayed by failure to start a service

Lennart Poettering composed on 2016-05-29 18:40 (UTC+0200): Felix Miata wrote: The message I see is equivalent in form as during boot, e.g. when a filesystem not noauto in fstab is to be mounted but cannot be found, so a delay of typically 90sec, but sometimes much longer, occurs. Mount speci

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

2016-05-29 18:28 GMT+02:00 Lennart Poettering : > On Sat, 28.05.16 21:38, Martin Pitt ([email protected]) wrote: > >> Chris Friesen [2016-05-27 9:14 -0600]: >> > The reason why I'm poking at this is that the old scheme worked "good >> > enough" for us for several years. Now of course the new

Re: [systemd-devel] shutdown delayed by failure to start a service

On Sat, 28.05.16 04:42, Felix Miata ([email protected]) wrote: > Mantas Mikulėnas composed on 2016-05-27 20:05 (UTC+0300): > > >Lennart Poettering wrote: > > >>Felix Miata wrote: > > >>>Did this ever get fixed? IOW, sometimes a service will fail to start when a > >>>system is started, or la

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

On Sat, 28.05.16 21:38, Martin Pitt ([email protected]) wrote: > Chris Friesen [2016-05-27 9:14 -0600]: > > The reason why I'm poking at this is that the old scheme worked "good > > enough" for us for several years. Now of course the new scheme is better, > > but it breaks backwards compati

[systemd-devel] Erlang bindings for systemd-notify API

Hello All! I'd like to introduce another systemd-related project - erlang-sd_notify. That's just a bindings for sd_notify API. Currently it implements bindings just for two functions - sd_notify and sd_notifyf, which is enough for using "Type=notify" as a service type. https://github.com/lemenkov/