Re: [systemd-devel] minimal-uclibc: systemd fails with `src/manager.c:257:42: error: 'EPOLL_CLOEXEC' undeclared (first use in this function)`

2011-05-10 Thread Thierry Reding
* Paul Menzel wrote: > Dear OE folks, > > > task compile of `systemd_git.bb` fails with the following error message > using `minimal-uclibc` for `MACHINE = "beagleboard"`. Using `minimal`, > i. e. EGLIBC, works. > > […] > | CC src/libsystemd_core_la-manager.lo > | s

Re: [systemd-devel] [PATCH] SELINUX: add /sys/fs/selinux mount point to put selinuxfs

2011-05-10 Thread Greg KH
On Tue, May 10, 2011 at 03:55:24PM -0700, Casey Schaufler wrote: > On 5/10/2011 3:34 PM, Greg KH wrote: > > From: Greg Kroah-Hartman > > > > In the interest of keeping userspace from having to create new root > > filesystems all the time, let's follow the lead of the other in-kernel > > filesystem

Re: [systemd-devel] [PATCH] SELINUX: add /sys/fs/selinux mount point to put selinuxfs

2011-05-10 Thread Casey Schaufler
On 5/10/2011 3:34 PM, Greg KH wrote: > From: Greg Kroah-Hartman > > In the interest of keeping userspace from having to create new root > filesystems all the time, let's follow the lead of the other in-kernel > filesystems and provide a proper mount point for it in sysfs. > > For selinuxfs, this m

[systemd-devel] [PATCH] SELINUX: add /sys/fs/selinux mount point to put selinuxfs

2011-05-10 Thread Greg KH
From: Greg Kroah-Hartman In the interest of keeping userspace from having to create new root filesystems all the time, let's follow the lead of the other in-kernel filesystems and provide a proper mount point for it in sysfs. For selinuxfs, this mount point should be in /sys/fs/selinux/ Cc: St

Re: [systemd-devel] minimal-uclibc: systemd fails with `src/manager.c:257:42: error: 'EPOLL_CLOEXEC' undeclared (first use in this function)`

2011-05-10 Thread Paul Menzel
Dear systemd folks, I am sorry for this message. I first wanted it to send to systemd-devel but decided to send it to openembedded-devel instead and forgot to update the address. If you have any insight though it is most welcome. Thanks, PAul signature.asc Description: This is a digitally si

Re: [systemd-devel] Failed to connect to socket /org/freedesktop/systemd1/private

2011-05-10 Thread Daniel Drake
On 9 May 2011 22:46, Lennart Poettering wrote: > You are lacking autofs4 support in the kernel. You should fix this first. I'm not, autofs4 is present, we're working on figuring out on why systemd complains at https://bugs.freedesktop.org/show_bug.cgi?id=36993 > Your udev in your initrd is a dif

[systemd-devel] minimal-uclibc: systemd fails with `src/manager.c:257:42: error: 'EPOLL_CLOEXEC' undeclared (first use in this function)`

2011-05-10 Thread Paul Menzel
Dear OE folks, task compile of `systemd_git.bb` fails with the following error message using `minimal-uclibc` for `MACHINE = "beagleboard"`. Using `minimal`, i. e. EGLIBC, works. […] | CC src/libsystemd_core_la-manager.lo | src/manager.c: In function 'manager_new':

Re: [systemd-devel] device units rely on udev rules?

2011-05-10 Thread Kay Sievers
On Tue, May 10, 2011 at 20:37, Koen Kooi wrote: >>> root@beagleboard-systemd:~# time ( udevadm trigger ; udevadm settle ) >>> >>> real    0m10.475s >> >> Ok, at least the timeout issue seems gone. >> >> How many device do you have? >>  find /sys -name uevent | wc -l > > root@beagleboard-systemd:/

[systemd-devel] [Patch V2] systemd-analyze: print hostname, kernelversion and arch at the top of the plot

2011-05-10 Thread Koen Kooi
Signed-off-by: Koen Kooi --- src/systemd-analyze |5 - 1 files changed, 4 insertions(+), 1 deletions(-) diff --git a/src/systemd-analyze b/src/systemd-analyze index 4f3e478..ae7dcfb 100755 --- a/src/systemd-analyze +++ b/src/systemd-analyze @@ -110,7 +110,7 @@ elif sys.argv[1] == 'blame'

Re: [systemd-devel] device units rely on udev rules?

2011-05-10 Thread Koen Kooi
Op 10 mei 2011, om 19:01 heeft Kay Sievers het volgende geschreven: > On Tue, May 10, 2011 at 17:34, Koen Kooi wrote: > >> So after rebuilding eglibc against 2.6.37 headers and udev from git: >> >> root@beagleboard-systemd:~# time ( udevadm trigger ; udevadm settle ) >> >> real0m10.475s >

[systemd-devel] [PATCH] systemd-analyze: print hostname and kernelversion at the top of the plot

2011-05-10 Thread Koen Kooi
Signed-off-by: Koen Kooi --- src/systemd-analyze |5 - 1 files changed, 4 insertions(+), 1 deletions(-) diff --git a/src/systemd-analyze b/src/systemd-analyze index 4f3e478..49a2727 100755 --- a/src/systemd-analyze +++ b/src/systemd-analyze @@ -110,7 +110,7 @@ elif sys.argv[1] == 'blame'

Re: [systemd-devel] how make reload=restart

2011-05-10 Thread Lennart Poettering
On Tue, 10.05.11 21:18, Alexey Shabalin (a.shaba...@gmail.com) wrote: > > > Instead, just use "systemctl reload-or-restart ..." in your client code > > and things will work fine. We added "reload-or-restart" precisely for > > use cases like this, so, go, use it! > > Sorry, but we must provide goo

Re: [systemd-devel] how make reload=restart

2011-05-10 Thread Alexey Shabalin
> Instead, just use "systemctl reload-or-restart ..." in your client code > and things will work fine. We added "reload-or-restart" precisely for > use cases like this, so, go, use it! Sorry, but we must provide good support systemd and SysV in our discributive. Our "service" knows nothing about "r

Re: [systemd-devel] [PATCH] {locale, vconsole}-setup.c: unconditionally read config file settings

2011-05-10 Thread Lennart Poettering
On Wed, 04.05.11 10:28, Harald Hoyer (har...@redhat.com) wrote: > > Am 03.05.2011 18:02, schrieb Lennart Poettering: > > On Tue, 03.05.11 16:39, har...@redhat.com (har...@redhat.com) wrote: > > > >> From: Harald Hoyer > >> > >> systemd-vconsole-setup did not process any configuration files, if

Re: [systemd-devel] device units rely on udev rules?

2011-05-10 Thread Kay Sievers
On Tue, May 10, 2011 at 17:34, Koen Kooi wrote: > So after rebuilding eglibc against 2.6.37 headers and udev from git: > > root@beagleboard-systemd:~# time ( udevadm trigger ; udevadm settle ) > > real    0m10.475s Ok, at least the timeout issue seems gone. How many device do you have? find /

Re: [systemd-devel] how make reload=restart

2011-05-10 Thread Lennart Poettering
On Tue, 10.05.11 20:50, Alexey Shabalin (a.shaba...@gmail.com) wrote: > > 2011/5/10 Lennart Poettering : > > On Tue, 10.05.11 20:03, Alexey Shabalin (a.shaba...@gmail.com) wrote: > > > >> Hello! > >> > >> Our logrotate after finish run script syslog-reload (detect syslog > >> daemon - sysklogd or

Re: [systemd-devel] [PATCH 2/2] user-sessions: don't report errors unless /{etc, run}/nologin exists and cannot be removed

2011-05-10 Thread Lennart Poettering
On Wed, 04.05.11 11:01, Michael Olbrich (m.olbr...@pengutronix.de) wrote: > on a read-only file-system 'unlink' returns EROFS (Read-only file > system) even if the file does not exists. To avoid false errors, > check if the file exists first. I now commited a different fix for this. Please test!

Re: [systemd-devel] how make reload=restart

2011-05-10 Thread Alexey Shabalin
2011/5/10 Lennart Poettering : > On Tue, 10.05.11 20:03, Alexey Shabalin (a.shaba...@gmail.com) wrote: > >> Hello! >> >> Our logrotate after finish run script syslog-reload (detect syslog >> daemon - sysklogd or syslog-ng or rsyslog, and run service foo reload) >> But some services do not support r

Re: [systemd-devel] [PATCH 1/2] create dbussystemservicedir

2011-05-10 Thread Lennart Poettering
On Wed, 04.05.11 11:01, Michael Olbrich (m.olbr...@pengutronix.de) wrote: > otherwise building fails if it doesn't exist: > > ( cd /usr/share/dbus-1/services && \ > rm -f org.freedesktop.systemd1.service && \ > ln -s ../system-services/org.freedesktop.systemd1.serv

Re: [systemd-devel] how make reload=restart

2011-05-10 Thread Alexey Shabalin
2011/5/10 "Jóhann B. Guðmundsson" : > On 05/10/2011 04:03 PM, Alexey Shabalin wrote: >> >> Hello! >> >> Our logrotate after finish run script syslog-reload (detect syslog >> daemon - sysklogd or syslog-ng or rsyslog, and run service foo reload) >> But some services do not support reload, for exampl

Re: [systemd-devel] how make reload=restart

2011-05-10 Thread Lennart Poettering
On Tue, 10.05.11 20:03, Alexey Shabalin (a.shaba...@gmail.com) wrote: > Hello! > > Our logrotate after finish run script syslog-reload (detect syslog > daemon - sysklogd or syslog-ng or rsyslog, and run service foo reload) > But some services do not support reload, for example rsyslog. > In init.

Re: [systemd-devel] Parallel startup with sockets and without killing the machine?

2011-05-10 Thread Lennart Poettering
On Tue, 10.05.11 09:25, Scott James Remnant (sc...@netsplit.com) wrote: > On Tue, May 10, 2011 at 7:41 AM, Gustavo Sverzut Barbieri < > barbi...@profusion.mobi> wrote: > > > I'm not following all the user-session discussion, but AFAIU this > > management will be done by the same code, but not sam

Re: [systemd-devel] how make reload=restart

2011-05-10 Thread Jóhann B. Guðmundsson
On 05/10/2011 04:03 PM, Alexey Shabalin wrote: Hello! Our logrotate after finish run script syslog-reload (detect syslog daemon - sysklogd or syslog-ng or rsyslog, and run service foo reload) But some services do not support reload, for example rsyslog. In init.d/rsyslog i can add reload=restart

Re: [systemd-devel] Parallel startup with sockets and without killing the machine?

2011-05-10 Thread Scott James Remnant
On Tue, May 10, 2011 at 7:41 AM, Gustavo Sverzut Barbieri < barbi...@profusion.mobi> wrote: > I'm not following all the user-session discussion, but AFAIU this > management will be done by the same code, but not same process (it's not > PID1). PAM (or another entity that has a role in the login/lo

[systemd-devel] how make reload=restart

2011-05-10 Thread Alexey Shabalin
Hello! Our logrotate after finish run script syslog-reload (detect syslog daemon - sysklogd or syslog-ng or rsyslog, and run service foo reload) But some services do not support reload, for example rsyslog. In init.d/rsyslog i can add reload=restart Very necessary add option to foo.service like Re

Re: [systemd-devel] Parallel startup with sockets and without killing the machine?

2011-05-10 Thread Lennart Poettering
On Mon, 09.05.11 19:52, Scott James Remnant (sc...@netsplit.com) wrote: > On Mon, May 9, 2011 at 12:16 PM, Gustavo Sverzut Barbieri < > barbi...@profusion.mobi> wrote: > > > > >> Well, right now let's make clear that Firefox/Chromium or other X clients > >> won't be started by systemd as they are

Re: [systemd-devel] Parallel startup with sockets and without killing the machine?

2011-05-10 Thread Lennart Poettering
On Mon, 09.05.11 19:49, Scott James Remnant (sc...@netsplit.com) wrote: > > We can now boot a resonably complete GNOME userspace in less than > > 1s. Given that that is the *total* these days, I really don't > > understand why you are concerned about the startup speed of individual > > service, an

Re: [systemd-devel] device units rely on udev rules?

2011-05-10 Thread Lennart Poettering
On Tue, 10.05.11 17:34, Koen Kooi (k...@dominion.thruhere.net) wrote: > > > Op 10 mei 2011, om 14:14 heeft Lennart Poettering het volgende geschreven: > > > On Tue, 10.05.11 14:11, Harald Hoyer (harald.ho...@gmail.com) wrote: > > > >> > >> Am 10.05.2011 14:09, schrieb Lennart Poettering: > >>

Re: [systemd-devel] device units rely on udev rules?

2011-05-10 Thread Koen Kooi
Op 10 mei 2011, om 14:14 heeft Lennart Poettering het volgende geschreven: > On Tue, 10.05.11 14:11, Harald Hoyer (harald.ho...@gmail.com) wrote: > >> >> Am 10.05.2011 14:09, schrieb Lennart Poettering: >>> On Tue, 10.05.11 13:47, Koen Kooi (k...@dominion.thruhere.net) wrote: >>> > What ud

Re: [systemd-devel] Parallel startup with sockets and without killing the machine?

2011-05-10 Thread Gustavo Sverzut Barbieri
On Mon, May 9, 2011 at 11:52 PM, Scott James Remnant wrote: > On Mon, May 9, 2011 at 12:16 PM, Gustavo Sverzut Barbieri < > barbi...@profusion.mobi> wrote: > >> >>> Well, right now let's make clear that Firefox/Chromium or other X clients >>> won't be started by systemd as they are user session ap

Re: [systemd-devel] device units rely on udev rules?

2011-05-10 Thread Koen Kooi
Op 10 mei 2011, om 14:14 heeft Lennart Poettering het volgende geschreven: > On Tue, 10.05.11 14:11, Harald Hoyer (harald.ho...@gmail.com) wrote: > >> >> Am 10.05.2011 14:09, schrieb Lennart Poettering: >>> On Tue, 10.05.11 13:47, Koen Kooi (k...@dominion.thruhere.net) wrote: >>> > What ud

Re: [systemd-devel] device units rely on udev rules?

2011-05-10 Thread Lennart Poettering
On Tue, 10.05.11 14:11, Harald Hoyer (harald.ho...@gmail.com) wrote: > > Am 10.05.2011 14:09, schrieb Lennart Poettering: > >On Tue, 10.05.11 13:47, Koen Kooi (k...@dominion.thruhere.net) wrote: > > > >>>What udev version is that? I'm running current -git, maybe something > >>>was broken, don't k

Re: [systemd-devel] device units rely on udev rules?

2011-05-10 Thread Kay Sievers
On Tue, May 10, 2011 at 14:11, Harald Hoyer wrote: > Am 10.05.2011 14:09, schrieb Lennart Poettering: >> >> On Tue, 10.05.11 13:47, Koen Kooi (k...@dominion.thruhere.net) wrote: >> What udev version is that? I'm running current -git, maybe something was broken, don't know it though. >>>

Re: [systemd-devel] device units rely on udev rules?

2011-05-10 Thread Harald Hoyer
Am 10.05.2011 14:09, schrieb Lennart Poettering: On Tue, 10.05.11 13:47, Koen Kooi (k...@dominion.thruhere.net) wrote: What udev version is that? I'm running current -git, maybe something was broken, don't know it though. [ 122.891967]<27>udevd[88]: unable to receive ctrl connection: Functio

Re: [systemd-devel] device units rely on udev rules?

2011-05-10 Thread Kay Sievers
On Tue, May 10, 2011 at 14:09, Lennart Poettering wrote: > On Tue, 10.05.11 13:47, Koen Kooi (k...@dominion.thruhere.net) wrote: > >> > What udev version is that? I'm running current -git, maybe something >> > was broken, don't know it though. >> >> [  122.891967] <27>udevd[88]: unable to receive

Re: [systemd-devel] device units rely on udev rules?

2011-05-10 Thread Lennart Poettering
On Tue, 10.05.11 13:47, Koen Kooi (k...@dominion.thruhere.net) wrote: > > What udev version is that? I'm running current -git, maybe something > > was broken, don't know it though. > > [ 122.891967] <27>udevd[88]: unable to receive ctrl connection: Function not > implemented > > Time to rebuil

Re: [systemd-devel] device units rely on udev rules?

2011-05-10 Thread Koen Kooi
Op 10 mei 2011, om 12:28 heeft Kay Sievers het volgende geschreven: > On Tue, May 10, 2011 at 12:22, Koen Kooi wrote: > It's 3 minutes exactly (+trigger and shell overhead) every time, so I guess I'm hitting some kind of timeout >>> >>> It's 180 sec, yeah. Doesn't it print what devi

Re: [systemd-devel] device units rely on udev rules?

2011-05-10 Thread Koen Kooi
Op 10 mei 2011, om 12:28 heeft Kay Sievers het volgende geschreven: > On Tue, May 10, 2011 at 12:22, Koen Kooi wrote: > It's 3 minutes exactly (+trigger and shell overhead) every time, so I guess I'm hitting some kind of timeout >>> >>> It's 180 sec, yeah. Doesn't it print what devi

Re: [systemd-devel] device units rely on udev rules?

2011-05-10 Thread Kay Sievers
On Tue, May 10, 2011 at 12:22, Koen Kooi wrote: >>> It's 3 minutes exactly (+trigger and shell overhead) every time, so I guess >>> I'm hitting some kind of timeout >> >> It's 180 sec, yeah. Doesn't it print what device it waited for? > > udevadm doesn't > >> If you add: "... settle --timeout=10

Re: [systemd-devel] device units rely on udev rules?

2011-05-10 Thread Koen Kooi
Op 10 mei 2011, om 11:55 heeft Kay Sievers het volgende geschreven: > On Tue, May 10, 2011 at 11:26, Koen Kooi wrote: >> >> Op 10 mei 2011, om 10:36 heeft Kay Sievers het volgende geschreven: >> >>> On Tue, May 10, 2011 at 10:26, Koen Kooi wrote: Op 9 mei 2011, om 22:23 heeft Kay Sievers

Re: [systemd-devel] device units rely on udev rules?

2011-05-10 Thread Kay Sievers
On Tue, May 10, 2011 at 11:26, Koen Kooi wrote: > > Op 10 mei 2011, om 10:36 heeft Kay Sievers het volgende geschreven: > >> On Tue, May 10, 2011 at 10:26, Koen Kooi wrote: >>> Op 9 mei 2011, om 22:23 heeft Kay Sievers het volgende geschreven: >> Things like:  time (udevadm trigger; ude

Re: [systemd-devel] device units rely on udev rules?

2011-05-10 Thread Koen Kooi
Op 10 mei 2011, om 10:36 heeft Kay Sievers het volgende geschreven: > On Tue, May 10, 2011 at 10:26, Koen Kooi wrote: >> Op 9 mei 2011, om 22:23 heeft Kay Sievers het volgende geschreven: > >>> Things like: >>> time (udevadm trigger; udevadm settle) >> >> root@beagleboard-systemd:~# time ( ud

Re: [systemd-devel] device units rely on udev rules?

2011-05-10 Thread Harald Hoyer
Am 10.05.2011 10:40, schrieb Harald Hoyer: Am 10.05.2011 10:36, schrieb Kay Sievers: On Tue, May 10, 2011 at 10:26, Koen Kooi wrote: Op 9 mei 2011, om 22:23 heeft Kay Sievers het volgende geschreven: Things like: time (udevadm trigger; udevadm settle) root@beagleboard-systemd:~# time ( ude

Re: [systemd-devel] device units rely on udev rules?

2011-05-10 Thread Harald Hoyer
Am 10.05.2011 10:36, schrieb Kay Sievers: On Tue, May 10, 2011 at 10:26, Koen Kooi wrote: Op 9 mei 2011, om 22:23 heeft Kay Sievers het volgende geschreven: Things like: time (udevadm trigger; udevadm settle) root@beagleboard-systemd:~# time ( udevadm trigger ; udevadm settle) real3

Re: [systemd-devel] device units rely on udev rules?

2011-05-10 Thread Kay Sievers
On Tue, May 10, 2011 at 10:26, Koen Kooi wrote: > Op 9 mei 2011, om 22:23 heeft Kay Sievers het volgende geschreven: >> Things like: >>  time (udevadm trigger; udevadm settle) > > root@beagleboard-systemd:~# time ( udevadm trigger ; udevadm settle) > > real    3m0.475s 3 Minutes? > UDEV  [13050

Re: [systemd-devel] device units rely on udev rules?

2011-05-10 Thread Koen Kooi
Op 9 mei 2011, om 22:23 heeft Kay Sievers het volgende geschreven: > On Mon, May 9, 2011 at 22:08, Lennart Poettering > wrote: >> On Mon, 09.05.11 22:02, Lennart Poettering (lenn...@poettering.net) wrote: >> It's still in the 10 second range on a 600MHz cortex-a8 machine booting from

Re: [systemd-devel] device units rely on udev rules?

2011-05-10 Thread Koen Kooi
Op 9 mei 2011, om 22:23 heeft Kay Sievers het volgende geschreven: > On Mon, May 9, 2011 at 22:08, Lennart Poettering > wrote: >> On Mon, 09.05.11 22:02, Lennart Poettering (lenn...@poettering.net) wrote: >> It's still in the 10 second range on a 600MHz cortex-a8 machine booting from