[systemd-devel] Rate limiting socket-activating services that fail to start

2013-06-14 Thread Andrey Borzenkov
I was testing behavior when syslog.service fails to start and found systemd taking 100% of CPU (core) time - 50% user, 50% system. See http://marc.info/?l=opensuse&m=137127774415206&w=2 Is it possible to rate limit socket activated service? I do not see any parameters in systemd.unit or systemd.so

Re: [systemd-devel] [PATCH v4] journalctl: Add support for showing messages from a previous boot

2013-06-14 Thread Zbigniew Jędrzejewski-Szmek
On Wed, Jun 12, 2013 at 02:41:15PM +0200, Jan Janssen wrote: > Unfortunately, to get a chronological list of boot IDs, we > need to search through the journal. sd_journal_enumerate_unique() > doesn't help us here, because the order of returned values > is undefined. Hi Jan, as an experiment, I tri

Re: [systemd-devel] [PATCH] systemd-analyze: Show critical chains for listed units

2013-06-14 Thread Zbigniew Jędrzejewski-Szmek
On Tue, Jun 11, 2013 at 10:29:32PM +0200, Gabriel de Perthuis wrote: > --- > src/analyze/systemd-analyze.c | 18 -- > 1 file changed, 12 insertions(+), 6 deletions(-) Applied. > Nb: it might be even better to show the critical chain of a fictive > unit that would depend on everyth

Re: [systemd-devel] [PATCH] man: improve readability of "_TRANSPORT=" section in systemd.journal-fields(7)

2013-06-14 Thread Zbigniew Jędrzejewski-Szmek
On Wed, Jun 12, 2013 at 07:45:14PM +0200, Jason St. John wrote: > From: "Jason St. John" > > The list and descriptions of valid transports was difficult to read, so > break the long sentence up into discrete man page list items to improve > readability. Applied. Zbyszek _

Re: [systemd-devel] [PATCH] rules: only run systemd-sysctl when a network device is added

2013-06-14 Thread Ross Lagerwall
On Fri, Jun 14, 2013 at 02:44:23PM +0200, Zbigniew Jędrzejewski-Szmek wrote: > On Thu, Jun 13, 2013 at 10:45:12AM +0100, Ross Lagerwall wrote: > > Otherwise, when a network device is renamed, systemd-sysctl is run twice > > with the same network device name: once for ACTION="add" and once for > > A

Re: [systemd-devel] [PATCH] rules: only run systemd-sysctl when a network device is added

2013-06-14 Thread Zbigniew Jędrzejewski-Szmek
On Thu, Jun 13, 2013 at 10:45:12AM +0100, Ross Lagerwall wrote: > Otherwise, when a network device is renamed, systemd-sysctl is run twice > with the same network device name: once for ACTION="add" and once for > ACTION="move". Hm, but if I have some sysctl for the network device, /proc/sys/net/ip

Re: [systemd-devel] [PATCH] udev hwdb: Store binary database in libdir, not in /etc

2013-06-14 Thread Tom Gundersen
Hi Martin, On Fri, Jun 14, 2013 at 2:15 PM, Martin Pitt wrote: > I tought about using /var/cache/ first as well, but /var might be on a > different partition. Hence I was using /lib/udev (i. e. udevlibdir) as > this guaranteed to be on the same partition as all the other udev > helpers. Yeah, I

Re: [systemd-devel] [PATCH] man: fix spacing issue in sd_is_fifo(3)

2013-06-14 Thread Zbigniew Jędrzejewski-Szmek
On Wed, Jun 12, 2013 at 09:25:08PM +0200, Jason St. John wrote: > From: "Jason St. John" > > Before: libsystemd-daemonpkg-config(1) > After: libsystemd-daemon pkg-config(1) > > This fix is more complicated than it should be due to the consecutive > XML elements separated by collapsible whitespac

Re: [systemd-devel] how to end a socket activated daemon

2013-06-14 Thread Zbigniew Jędrzejewski-Szmek
On Fri, Jun 14, 2013 at 10:03:00AM +0200, Łukasz Stelmach wrote: > Hi. > > We are converting some daemons to socket activation. Most of them open > unix sockets and manage incoming connections in a main-loop, so the > easiest way to convert it is to create Accept=false socket with systemd. > > No

Re: [systemd-devel] [PATCH] udev hwdb: Store binary database in libdir, not in /etc

2013-06-14 Thread Martin Pitt
Hello Tom, Tom Gundersen [2013-06-14 13:08 +0200]: > That said, I don't think libdir is appropriate as this data is not > under the control of the package manager (as it is generated at > install-time rather than at build-time, it would for instance not be > suitable for sharing between hosts). I

Re: [systemd-devel] [PATCH] udev hwdb: Store binary database in libdir, not in /etc

2013-06-14 Thread Tom Gundersen
On Fri, Jun 14, 2013 at 2:03 PM, Łukasz Stelmach wrote: > It was <2013-06-14 pią 13:30>, when Jan Janssen wrote: >> On 06/14/2013 01:08 PM, Tom Gundersen wrote: >>> That said, I don't think libdir is appropriate as this data is not >>> under the control of the package manager (as it is generated a

Re: [systemd-devel] [PATCH] udev hwdb: Store binary database in libdir, not in /etc

2013-06-14 Thread Łukasz Stelmach
It was <2013-06-14 pią 13:30>, when Jan Janssen wrote: > On 06/14/2013 01:08 PM, Tom Gundersen wrote: >> That said, I don't think libdir is appropriate as this data is not >> under the control of the package manager (as it is generated at >> install-time rather than at build-time, it would for inst

Re: [systemd-devel] [PATCH] udev hwdb: Store binary database in libdir, not in /etc

2013-06-14 Thread Jan Janssen
On 06/14/2013 01:08 PM, Tom Gundersen wrote: That said, I don't think libdir is appropriate as this data is not under the control of the package manager (as it is generated at install-time rather than at build-time, it would for instance not be suitable for sharing between hosts). I guess localst

Re: [systemd-devel] [PATCH] udev hwdb: Store binary database in libdir, not in /etc

2013-06-14 Thread Tom Gundersen
On Fri, Jun 14, 2013 at 12:26 PM, Martin Pitt wrote: > right now, udev stores its binary hwdb cache in /etc/udev/, which is > ugly IMHO. This is neither user-editable nor configuration of any > kind. It's just a cache file, and does not need to appear in backup, > VCSes of /etc and the like. > > C

[systemd-devel] [PATCH] udev hwdb: Store binary database in libdir, not in /etc

2013-06-14 Thread Martin Pitt
Hello all, right now, udev stores its binary hwdb cache in /etc/udev/, which is ugly IMHO. This is neither user-editable nor configuration of any kind. It's just a cache file, and does not need to appear in backup, VCSes of /etc and the like. Can we move it to the libdir instead? Attached patch d

[systemd-devel] how to end a socket activated daemon

2013-06-14 Thread Łukasz Stelmach
Hi. We are converting some daemons to socket activation. Most of them open unix sockets and manage incoming connections in a main-loop, so the easiest way to convert it is to create Accept=false socket with systemd. Now, it is quite well described how to start such daemon, however, there is littl