Re: Read-only rootfs on systemd

2014-03-07 Thread Reco
On Thu, Mar 06, 2014 at 11:05:20PM +, Amit wrote: 0) After reboot and running 'lsof +L1': COMMAND PID USER FD TYPE DEVICE SIZE/OFF NLINK NODE NAME cupsd935 root8r REG8,1 1392 0 132095 /etc/passwd (deleted) So it's reproducible. 1) Shutting

Re: Read-only rootfs on systemd

2014-03-07 Thread Brian
On Thu 06 Mar 2014 at 23:05:20 +, Amit wrote: 0) After reboot and running 'lsof +L1': COMMAND PID USER FD TYPE DEVICE SIZE/OFF NLINK NODE NAME cupsd935 root8r REG8,1 1392 0 132095 /etc/passwd (deleted) I upgraded my wheezy install to jessie

Re: Read-only rootfs on systemd [SOLVED]

2014-03-07 Thread Amit
Thanks for your help and the replies. So this issue is now resolved. Summary of Issue: Mounting root as read-only as documented in (https://wiki.debian.org/ReadonlyRoot) because rootfs is busy. Summary of Solution: 1. 'lsof +L1' showed cupsd getting stuck on /etc/passwd (deleted). Looking

Re: Read-only rootfs on systemd

2014-03-06 Thread Brian
On Thu 06 Mar 2014 at 01:21:03 +, Amit wrote: I need cups, so is there a way around this? This doesn't answer your question but I have a spare Wheezy with separate /, /home, and /var. I installed systemd, made the rootfs ro in fstab and booted with init=/lib/systemd/systemd. The rootfs was

Re: Read-only rootfs on systemd

2014-03-06 Thread Robin
On 6 March 2014 01:21, Amit amit.ut...@gmail.com wrote: Amit amit.uttam at gmail.com writes: [snip] However, setting up a fresh install of systemd, the readonly does not have any effect. The rootfs is still mounted as rw. All I did was changed /etc/fstab. Based on the systemd man pages,

Re: Read-only rootfs on systemd

2014-03-06 Thread Reco
Hi. On Thu, 6 Mar 2014 14:49:30 + Brian a...@cityscape.co.uk wrote: On Thu 06 Mar 2014 at 01:21:03 +, Amit wrote: I need cups, so is there a way around this? This doesn't answer your question but I have a spare Wheezy with separate /, /home, and /var. I installed systemd, made

Re: Read-only rootfs on systemd

2014-03-06 Thread Amit
Reco recoverym4n at gmail.com writes: https://wiki.debian.org/ReadonlyRoot#cups says: CUPS stores any kind of state files under /etc (classes.conf, cupsd.conf, printers.conf subscriptions.conf) and upstream is against any modification. Personally I worked around similar problem by

Re: Read-only rootfs on systemd

2014-03-06 Thread Amit
Robin rc.rattusrattus at gmail.com writes: Just a suggestion have you tried a re-install of cups since fresh install of systemd Thanks for the reply. Yes, the first thing I did was install systemd and then all the other packages but anyways I tried reinstalling again but no luck. -- To

Re: Read-only rootfs on systemd

2014-03-06 Thread Amit
Brian ad44 at cityscape.co.uk writes: On Thu 06 Mar 2014 at 01:21:03 +, Amit wrote: I need cups, so is there a way around this? This doesn't answer your question but I have a spare Wheezy with separate /, /home, and /var. I installed systemd, made the rootfs ro in fstab and booted

Re: Read-only rootfs on systemd

2014-03-06 Thread Reco
On Thu, 6 Mar 2014 18:35:06 + (UTC) Amit amit.ut...@gmail.com wrote: Reco recoverym4n at gmail.com writes: https://wiki.debian.org/ReadonlyRoot#cups says: CUPS stores any kind of state files under /etc (classes.conf, cupsd.conf, printers.conf subscriptions.conf) and upstream is

Re: Read-only rootfs on systemd

2014-03-06 Thread Amit
Reco recoverym4n at gmail.com writes: Can you do the following, please: 1) Shutdown cups by systemd's way (systemctl blahblah …). 2) Start it by /etc/init.d/cups start. 3) Confirm with lsof whenever /etc/passwd is kept open. 4) While you're at it, invoke 'fuser /etc/passwd' to

Re: Read-only rootfs on systemd

2014-03-05 Thread Amit
Amit amit.uttam at gmail.com writes: [snip] However, setting up a fresh install of systemd, the readonly does not have any effect. The rootfs is still mounted as rw. All I did was changed /etc/fstab. Based on the systemd man pages, this should be enough. How do I go about

Read-only rootfs on systemd

2014-03-04 Thread Amit
Hello, I always run my debian systems with a separate /, /home, and /var. I added read-only 'ro' mount to fstab for the root / partition. So far it has been working great. However, setting up a fresh install of systemd, the readonly does not have any effect. The rootfs is still mounted as rw.