On Tue, Jun 21, 2011 at 3:45 PM, Maarten Lankhorst
wrote:
> Hey William,
>
> On 06/21/2011 06:50 AM, William Douglas wrote:
>> Lennart Poettering writes:
>>
>>> In general I must say that I actually like the code (and the coding
>>> style) very much, so it's hard for me to say no to this.
>>>
>>>
Hey William,
On 06/21/2011 06:50 AM, William Douglas wrote:
> Lennart Poettering writes:
>
>> In general I must say that I actually like the code (and the coding
>> style) very much, so it's hard for me to say no to this.
>>
>> KUTGW,
>>
>> Lennart
> I understand your reasoning and, though I'm di
/etc/rc.local is a symlink.
---
units/fedora/rc-local.service |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/units/fedora/rc-local.service b/units/fedora/rc-local.service
index a21a557..8c0b200 100644
--- a/units/fedora/rc-local.service
+++ b/units/fedora/rc-local.serv
On Tue, 21.06.11 20:06, Stef Bon ([email protected]) wrote:
> Hi,
>
> thanks for your info.
>
> I've got the following log output.
> Somewhere the message appears:
>
> remount-rootfs.service: cgroup is empty
This is just a debug message, not really a problem. You only get this
when debug loggi
Hi,
thanks for your info.
I've got the following log output.
Somewhere the message appears:
remount-rootfs.service: cgroup is empty
and after that different timeouts
I have a linux-2.6.39.1 kernel, automatic mounting devtmpfs enabled,
systemd 2.9.
Stef
Jun 21 18:33:07 Loaded 19088 symbol
On Tue, 21.06.11 18:50, Marius Tolzmann ([email protected]) wrote:
> > but it should be doing:
> >
> >fork() > fork() --> write_pid_file()
> >wait_for_notify()exit() notify_grandparent()
> >exit() run_main_loop()
> >
On 06/21/11 08:24, Stef Bon wrote:
> 2011/6/20 Marius Tolzmann :
>> Hi there..
>>
>> we are also using a self-maintained LFS based gnu/linux here.
>>
>> we switched to systemd in Nov 2010 and it worked fine from the start..
>
> What version are you using?
currently systemd v27 on production works
hi..
On 06/20/11 21:36, Lennart Poettering wrote:
>
> This very much sounds as if the service does not wait in the top-level
> process that the daemon process is properly forked and finished writing
> the PID file. systemd tries to read the PID file immediately after the
> top-level process exit
On Tue, 21.06.11 17:24, Sérgio Basto ([email protected]) wrote:
>
> On Tue, 2011-06-21 at 12:35 +0200, Lennart Poettering wrote:
> > These units are *not* installed locally,
> but I want install it , how I do know what should install ?
But why would you want that?
(If you really do, you can al
On Tue, 2011-06-21 at 12:35 +0200, Lennart Poettering wrote:
> These units are *not* installed locally,
but I want install it , how I do know what should install ?
Thanks,
--
Sérgio M. B.
___
systemd-devel mailing list
[email protected]
On Tue, 21.06.11 03:40, Sérgio Basto ([email protected]) wrote:
> > These units are referenced by other units (for example, because they
> > want to be ordered after or before them if both are installed), however
> > do not exist locally. That's why we cannot load them. To make this
> > less confu
11 matches
Mail list logo
