Theodore Ts'o (Tuesday 2015-01-13):
> My understanding is that the release team is trying very hard to get
> Jessie out the door, and so I don't want to try to push things,
> especially since most debian users probably won't have discovered this
> particular e2fsck.conf feature.
I understand. At least, future versions of e2fsck will have the fix.
> Well, the -C option is to date only honored by e2fsck. In fact
> /sbin/fsck will only pass the -C option to fsck.ext[234].
Ah, I hadn't noticed. systemd-fsck does pass the -C option to /sbin/fsck,
for all filesystem types, as long as fsck.<fstype> exists in the PATH (and
isn't a symlink to /bin/true or the like).
So, if other fsck programs detach a child process, they won't even be able
to close the pipe's fd and will have the problem. Do you know of any such?
> If I have time I'll have take a look at
> the systemd-fsck sources, but that's neither here nor there.
I have looked; if you think someone may be actually interested in a patch,
I could probably write it while the memory's fresh. It's not that hard,
just somewhat tedious, as you couldn't use fscanf reliably on the pipe
itself; you'd need a poll() loop that relays the pipe to a memory stream
or something like that. Do you think it would be worth it?
> For that matter, I wasn't aware that anyone other than Ubuntu's
> graphical boot is using it --- I have no idea why systemd-fsck would
> care about the progress bar information, and how or why it might be
> using it in the first place.
It writes a completion percentage to the console. As for why it doesn't
just use "-C0", I don't know.
All the best,
Cedric.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
