[Bug 605687] Re: mountall does everything twice

2012-07-19 Thread Launchpad Bug Tracker
[Expired for mountall (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mountall (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 605687] Re: mountall does everything twice

2012-05-19 Thread Steve Langasek
Hi Rob, This is quite an unusual bug. There have been no other reports of this behavior from mountall, but I see from your boot log that mountall is clearly processing all the mounts twice. Is this reproducible for you with more recent versions? ** Changed in: mountall (Ubuntu) Status:

[Bug 605687] Re: mountall does everything twice

2010-07-18 Thread Rob Donovan
I spent another half day or so on this. I didn't really get anywhere but I think the evidence is that neither the mountall.conf main script nor mountall itself actually restart (the script doesn't echo and the 2nd set of fscks don't show the parse_filesystems comments of the first, which are

[Bug 605687] Re: mountall does everything twice

2010-07-16 Thread Rob Donovan
1) I added 4 echo statements to each script in mountall.conf and can now say with no doubt that the main script runs once, and the post-stop script runs twice. I don't know how this can happen, but it does. 2) I added echo statements to both scripts in mountall-shell.conf too, also changing

[Bug 605687] Re: mountall does everything twice

2010-07-15 Thread Rob Donovan
** Summary changed: - mountall runs fsck, all clean, mounts, twice... out of boredom? + mountall does everything twice -- mountall does everything twice https://bugs.launchpad.net/bugs/605687 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 605687] Re: mountall does everything twice

2010-07-15 Thread Rob Donovan
It seems upscmd ups shutdown.stayoff does simply power off the load after all. I downloaded the nut source package and everything I saw pointed that way. I couldn't find any evidence of the code writing flags or commands to disk, though I admit I lost track of things through the socket. So, I