Re: [systemd-devel] run no more than one of [email protected] at a time

> On Oct 5, 2015, at 14:29, David Timothy Strauss > wrote: > > If you only want one instance running, why not just create one service and > reconfigure/restart it? > Because the service dependencies are totally different. > > On Mon, Oct 5, 2015, 09:04 Johannes Ernst

Re: [systemd-devel] run no more than one of [email protected] at a time

If you only want one instance running, why not just create one service and reconfigure/restart it? On Mon, Oct 5, 2015, 09:04 Johannes Ernst wrote: > I have a [email protected]. When started as > systemctl start foo@abc > I’d like all other currently active foo@… services to stop, and vice >

Re: [systemd-devel] Showing a more accurate version of systemd with the git sha1

On Fri, Oct 2, 2015 at 7:17 PM, Andrei Borzenkov wrote: > 02.10.2015 19:27, Francis Moreau пишет: >> >> Hello, >> >> I'd like to know if it would be possible to show the git version (the >> one given by git-describe) when using the systemd binaries with >> --version option. >> >> That would be spe

[systemd-devel] run no more than one of [email protected] at a time

I have a [email protected]. When started as systemctl start foo@abc I’d like all other currently active foo@… services to stop, and vice versa. All of the [email protected] are supposed to be mutually exclusive with each other. In [email protected], I attempted: Conflicts: [email protected] but that

[systemd-devel] Machinectl shell/login do not attach to console

Hi all, I have an Arch machine with systemd 226, running an Arch container, also with systemd 226. For whatever reason in 225, `machinectl login` stopped working correctly, and in 226 `machinectl login` does not work properly. It attaches to the machine, but does not seem to redirect stdin and

Re: [systemd-devel] First steps with sd-bus

I was missing the XML policy file. After creating one, it worked flawlessly. Thank you very much Daniel, One more question, I have been looking at systemd public man pages[0] as the sd-bus API reference, but I can't find documentation about some functions. For example information regarding vtable

Re: [systemd-devel] [PATCH] gssd: Improve scalability by not waiting for child processes

On 10/04/2015 04:19 AM, Florian Weimer wrote: > * Steve Dickson: > >> +static void >> +sig_child(int signal) >> +{ >> +int err; >> +pid_t pid; >> + >> +/* Parent: just wait on child to exit and return */ >> +do { >> +pid = wait(&err); >> +} while(pid == -1 && errn

Re: [systemd-devel] First steps with sd-bus

On 10/05/2015 12:59 PM, Iñigo Martínez wrote: > In a home made daemon, I needed to change some variables while > running, so I though about D-Bus as IPC and gived a chance to sd-bus. > > Let's say that I'm trying it on a development system (currently a > debian jessie) without any users on it, jus

[systemd-devel] First steps with sd-bus

In a home made daemon, I needed to change some variables while running, so I though about D-Bus as IPC and gived a chance to sd-bus. Let's say that I'm trying it on a development system (currently a debian jessie) without any users on it, just root, and some basic libraries and configuration. Aft

[systemd-devel] systemd shutdown query

Hello there, I have two queries Some processes terminated immediately after writing reboot before reaching systemd unit ExecStop 1. which processes are terminated by systemd during early phase of shutdown ? 2. Is this somewhat changeable, configurable? -- Thanks & Regards, Dushyant Uge __

Re: [systemd-devel] systemd and hostname supplied by DHCP

On Mon, Oct 5, 2015 at 9:28 AM, Alessio Igor Bogani < [email protected]> wrote: > Hi, > > On 3 October 2015 at 15:34, Lennart Poettering > wrote: > [...] > > Well, we need some kind of policy framework in place there that allows > > the "systemd-networkd" user to set the hostname. If yo

Re: [systemd-devel] systemd and hostname supplied by DHCP

On Mon, Oct 5, 2015 at 8:28 AM, Alessio Igor Bogani wrote: > So I'll install polkit. The only downside is that polkit drag > Javascript interpreter in which isn't a typical package for an > embedded system due it's footprint but I suspect that I should live > with it. :-) Yeah, that was a weird