Quoting Martinx - ジェームズ (thiagocmarti...@gmail.com): > On 12 March 2015 at 01:13, Don Armstrong <d...@debian.org> wrote: > > On Wed, 11 Mar 2015, The Wanderer wrote: > >> Running those commands doesn't give you output from 'systemctl stop > >> foo' or the like, however. [...] > > I suppose someone could make an argument that including a verbose flag > > or something might be useful, but considering that you can achieve > > similar functionality with existing discrete tools, I'm not sure that > > growing additional code and documentation to support such an option is > > worth it.
As Vincent pointed out, this is on a todo list. > > Look at the definition of start_unit in > > http://cgit.freedesktop.org/systemd/systemd/tree/src/systemctl/systemctl.c > > for the current code. 7½K of C? No thanks! > By not "polluting" the Linux boot with "starting this [OK]", "starting > that [OK]".... The Debian boot is now more "clear" with systemd, then, > if I need a feedback, I can ask for it... How? If I don't have "quiet" in the kernel parameters line, I get something that looks like dmesg on steroids, and it's impossible to tell what's going on at all. OTOH with it, and I'm lucky to get anything at all. I just sit and wait for a "clear-screen" (why does it do that and how do I stop it? Is there a dont-clear-screen.service?) and a login prompt. On random occasions, some messages do appear, just a little more verbose than is convenient, but an improvement. However, these messages usually mean trouble, and I finish up waiting for some service to start, with no limit on the wait (Bug#778881) and have to reboot. Sometimes, I get a stalled shutdown in a similar manner, so I have to hard-reset. If, as a result, the system decides to fsck the disk, systemd gives no indication of the fact. Actually it's the same if you force a full fsck with the kernel parameter: when systemd fscks the root filesytem, all you see is that the disk is busy. You only get progress % when it checks the other filesystems later on. Cheers, David. -- 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/20150312165104.gb7...@alum.home
