On 05/11/2014 08:29 AM, Michael Biebl wrote:
Am 11.05.2014 09:35, schrieb Sven Joachim:
Something like "journalctl -b | grep systemd-fsck". I haven't figured
out how to get "journalctl -u" to work here.
That, or something like
systemctl status systemd-fsck-root.service
or
systemctl status systemd-fsck@<your device>.service
works for me as well.
If you use
systemctl status systemd-fsck@<TAB>
autocompeltion will help you with choosing the right device name, *but*
make sure to properly quote the string, if it contains \, ie. either put
it in "" or use \\ instead of single \.
Yes, indeed, the first of these two commands provided the information I
was looking form. I'm going to have to read about systemctl.
The second command didn't seem to provide information about the fsck
output, but I may have been using it improperly.
And I learned something about my terminal emulator that I need to
correct. Apparently tab completion isn't operating on my system.
I'll do a little homework on that. It's obviously a useful tool.
HTH,
Michael
It does help, Michael. Thanks.
Best regards,
Jape
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/536fa43a.50...@comcast.net
