Op 9 mei 2011, om 22:23 heeft Kay Sievers het volgende geschreven:
On Mon, May 9, 2011 at 22:08, Lennart Poettering lenn...@poettering.net
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
On Tue, May 10, 2011 at 10:26, Koen Kooi k...@dominion.thruhere.net 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
Am 10.05.2011 10:36, schrieb Kay Sievers:
On Tue, May 10, 2011 at 10:26, Koen Kooik...@dominion.thruhere.net 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 ;
Op 10 mei 2011, om 10:36 heeft Kay Sievers het volgende geschreven:
On Tue, May 10, 2011 at 10:26, Koen Kooi k...@dominion.thruhere.net wrote:
Op 9 mei 2011, om 22:23 heeft Kay Sievers het volgende geschreven:
Things like:
time (udevadm trigger; udevadm settle)
On Tue, May 10, 2011 at 11:26, Koen Kooi k...@dominion.thruhere.net wrote:
Op 10 mei 2011, om 10:36 heeft Kay Sievers het volgende geschreven:
On Tue, May 10, 2011 at 10:26, Koen Kooi k...@dominion.thruhere.net wrote:
Op 9 mei 2011, om 22:23 heeft Kay Sievers het volgende geschreven:
Things
Op 10 mei 2011, om 11:55 heeft Kay Sievers het volgende geschreven:
On Tue, May 10, 2011 at 11:26, Koen Kooi k...@dominion.thruhere.net wrote:
Op 10 mei 2011, om 10:36 heeft Kay Sievers het volgende geschreven:
On Tue, May 10, 2011 at 10:26, Koen Kooi k...@dominion.thruhere.net wrote:
Op
On Tue, May 10, 2011 at 12:22, Koen Kooi k...@dominion.thruhere.net 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
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]27udevd[88]: unable to receive ctrl connection: Function
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 know it
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 udev version is
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 user
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
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
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
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 same
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
2011/5/10 Jóhann B. Guðmundsson johan...@gmail.com:
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
On Wed, 04.05.11 11:01, Michael Olbrich (m.olbr...@pengutronix.de) wrote:
otherwise building fails if it doesn't exist:
( cd DESTDIR/usr/share/dbus-1/services \
rm -f org.freedesktop.systemd1.service \
ln -s
2011/5/10 Lennart Poettering lenn...@poettering.net:
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
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!
On Tue, 10.05.11 20:50, Alexey Shabalin (a.shaba...@gmail.com) wrote:
2011/5/10 Lennart Poettering lenn...@poettering.net:
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 -
On Tue, May 10, 2011 at 17:34, Koen Kooi k...@dominion.thruhere.net 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
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 har...@redhat.com
systemd-vconsole-setup did not process any configuration files,
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 good support
Op 10 mei 2011, om 19:01 heeft Kay Sievers het volgende geschreven:
On Tue, May 10, 2011 at 17:34, Koen Kooi k...@dominion.thruhere.net wrote:
So after rebuilding eglibc against 2.6.37 headers and udev from git:
root@beagleboard-systemd:~# time ( udevadm trigger ; udevadm settle )
real
On Tue, May 10, 2011 at 20:37, Koen Kooi k...@dominion.thruhere.net 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
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':
On 9 May 2011 22:46, Lennart Poettering lenn...@poettering.net 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
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
From: Greg Kroah-Hartman gre...@suse.de
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
On 5/10/2011 3:34 PM, Greg KH wrote:
From: Greg Kroah-Hartman gre...@suse.de
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
* 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
|
32 matches
Mail list logo
