[systemd-devel] After in new var-lock.service

2010-08-18 Thread jean-michel.poll...@laposte.net
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.net
___
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] After in new var-lock.service

2010-08-18 Thread jean-michel.poll...@laposte.net

> 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 what I don't understand is, if the call to var-lock.service after 
var-lock.mount is implicit, why does var-run.service also need a 
"After=var-run.mount"? Both var-lock.service and var-run.service have the same 
"After=var-run.mount".
Isn't this specific to Fedora?

Une messagerie gratuite, garantie à vie et des services en plus, ça vous tente ?
Je crée ma boîte mail www.laposte.net

___
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel


[systemd-devel] systemd-clean and large files

2011-04-25 Thread jean-michel.poll...@laposte.net

 Hi,

I'm trying to use the systemd-tmpfiles-clean service with a backup directory, 
but it always fails to start, with the "Value too large for defined data type" 
error, which I think means largefile support is not enabled by default on these 
tools (I'm on a 32 bit system) and probably others, as I have lots of files > 
2GB in this directory.
Is this intentional or a bug?
I think that's a bug anyway, as that means that putting a correct conf file in 
/etc/tmpfiles.d can make the service fail, so /tmp and other directories will 
not be cleaned. Supporting largefile would be nice though.

Une messagerie gratuite, garantie à vie et des services en plus, ça vous tente ?
Je crée ma boîte mail www.laposte.net

___
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] systemd-clean and large files

2011-04-26 Thread jean-michel.poll...@laposte.net

> Message du 25/04/11 19:30
> De : "Kay Sievers" 
> A : "[email protected]" 
> Copie à : [email protected]
> Objet : Re: [systemd-devel] systemd-clean and large files
>
> 
> > I think that's a bug anyway, as that means that putting a correct conf file 
> > in /etc/tmpfiles.d can make the service fail, so /tmp and other directories 
> > will not be cleaned. Supporting largefile would be nice though.
> 
> Does adding:
> AC_SYS_LARGEFILE
> to:
> configure.ac
> make it work?
> 

It works perfectly now, thanks.

Une messagerie gratuite, garantie à vie et des services en plus, ça vous tente ?
Je crée ma boîte mail www.laposte.net

___
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] [PATCH] Move /tmp and /var/tmp to a separate tmpfiles.d file to ease overrides via /etc

2011-08-15 Thread jean-michel.poll...@laposte.net



> Message du 07/08/11 00:49
> De : "Josh Triplett" 
> A : [email protected]
> Copie à : 
> Objet : [systemd-devel] [PATCH] Move /tmp and /var/tmp to a separate 
> tmpfiles.d file to ease overrides via /etc
>
> Many people prefer to avoid clearing /tmp and /var/tmp, and
> distributions often have explicit settings for how often to clear them
> if at all. Overriding those with systemd currently requires overriding
> all of /usr/lib/tmpfiles.d/systemd.conf via
> /etc/tmpfiles.d/systemd.conf, copying across all the other entries, and
> updating that override when systemd.conf changes.
> 
> Move the /tmp and /var/tmp entries from systemd.conf to a separate
> tmp.conf, making them easier to override without affecting the rest of
> systemd.conf.
> ---
> 
> This change will allow me to create a personal package which ships
> /etc/tmpfiles.d/tmp.conf, without having to include the remainder of
> systemd.conf and update the package every time systemd.conf changes.


Regarding this issue, there's also the fact that the default files do not clear 
/tmp as they are.
Is it OK to default the type to "D" instead of "d" for /tmp in the systemd.conf 
file, so that it is cleared on boot?

Une messagerie gratuite, garantie à vie et des services en plus, ça vous tente ?
Je crée ma boîte mail www.laposte.net
___
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel