[systemd-devel] [PATCH] tmpfiles: try to handle read-only file systems gracefully

2015-04-30 Thread Michael Olbrich
On read-only filesystems trying to create the target will not fail with EEXIST but with EROFS. Handle EROFS by checking if the target already exists, and if empty when truncating. This avoids reporting errors if tmpfiles doesn't actually needs to do anything. --- This is a rework of a patch I wrot

Re: [systemd-devel] [PATCH] tmpfiles: try to handle read-only file systems gracefully

2015-04-30 Thread systemd github import bot
Patchset imported to github. Pull request: -- Generated by https://github.com/haraldh/mail2git ___ systemd-devel

Re: [systemd-devel] [PATCH] tmpfiles: try to handle read-only file systems gracefully

2015-05-05 Thread Zbigniew Jędrzejewski-Szmek
On Thu, Apr 30, 2015 at 08:50:38PM +0200, Michael Olbrich wrote: > On read-only filesystems trying to create the target will not fail with > EEXIST but with EROFS. Handle EROFS by checking if the target already > exists, and if empty when truncating. > This avoids reporting errors if tmpfiles doesn

Re: [systemd-devel] [PATCH] tmpfiles: try to handle read-only file systems gracefully

2015-05-06 Thread Michael Olbrich
On Wed, May 06, 2015 at 04:11:57AM +, Zbigniew Jędrzejewski-Szmek wrote: > On Thu, Apr 30, 2015 at 08:50:38PM +0200, Michael Olbrich wrote: > > On read-only filesystems trying to create the target will not fail with > > EEXIST but with EROFS. Handle EROFS by checking if the target already > > e