On Tue, May 10, 2011 at 06:57:11PM +0200, Lennart Poettering wrote:
> 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
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 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'm not sure if this is the correct fix, but generating an error when
/etc/nologin never existed is certainly a bug.
Regards,
Mic