On Wed, 18.08.10 21:31, [email protected]
([email protected]) wrote:
>
> > It creates stuff in /var/run that is only needed when an empty tmpfs
> > is mounted there. If /var/run is on disk, none of these things is
> > needed, but old stuff would need to be deleted ins
On Wed, 18.08.10 16:27, Matthias Clasen ([email protected]) wrote:
Heya,
> here is a patch to fix a small typo in the systemd dbus introspection data.
> I found this while trying to explore the systemd dbus API via bash
> completion with gdbus. You should try this, it is really fun, and,
Hey,
here is a patch to fix a small typo in the systemd dbus introspection data.
I found this while trying to explore the systemd dbus API via bash
completion with gdbus. You should try this, it is really fun, and,
evidently, helps to find some bugs...
Matthias
diff -up systemd-7/src/dbus-manage
> It creates stuff in /var/run that is only needed when an empty tmpfs
> is mounted there. If /var/run is on disk, none of these things is
> needed, but old stuff would need to be deleted instead. The .service
> is just the extension of the .mount, and does not make sense on its
> own.
OK
But wha
On Wed, Aug 18, 2010 at 17:55, [email protected]
wrote:
>
> I've seen that the new var-lock.service have a dependency
> "After=var-run.mount".
> Is there a specific reason why var-lock.service depends on var-run.mount
> being up ?
It creates stuff in /var/run that is only needed w
Hi Kay,
I've seen that the new var-lock.service have a dependency "After=var-run.mount".
Is there a specific reason why var-lock.service depends on var-run.mount being
up ?
Thanks
Une messagerie gratuite, garantie à vie et des services en plus, ça vous tente ?
Je crée ma boîte mail www.laposte.n
