Re: [systemd-devel] Verbose output option when starting daemons manually
On Thu, 08.11.12 18:23, William Giokas (1007...@gmail.com) wrote: > All, Heya, > I have been using systemd for a few months now, and I must say, it is a > great init system. I myself am no coder, else I would attempt to write > something to do just this. One not-dealbreaking thing that I do find > lacking is a verbose option for `systemctl start `, essentially > running `journalctl -f -u ` (and possibly for multiple dependent > units as well). For most services, I feel like this would be a line or > two of output just saying "It worked!" or "It broke!" but for services > like netcfg@, or services that start dependencies, it could be useful to > see what's getting started and how it's getting started. Again, feel free > to ignore me, I don't know how feasible or practical this would be, but > it seems like it would be useful. > > Again, sorry that I cannot put something together myself to at least > show you. I have added to the TODO list that we should have a mode where systemctl start/stop/... show in a single line what they did. Lennart -- Lennart Poettering - Red Hat, Inc. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Verbose output option when starting daemons manually
On Fri, Nov 09, 2012 at 12:45:22AM +, "Jóhann B. Guðmundsson" wrote: > What's lacking is the status to be shown when units are manually > started/reloaded/restart/stopped there is just one slight problem > implementing that which is you dont want that output when the > service is started at boot time or shutdown... > > perhaps that could be solved by introducing specific boot-start and > shutdown-stop switches which would only be used to start unit or > shut down units at boot-up/shutdown We already have verbose indicator, used on boot-up/shutdown; it is responsible for pretty display of Starting foo... [ OK ] Started foo. So this would be if (istty() && !show_status) do the journal output -- Tomasz Torcz 72->| 80->| xmpp: zdzich...@chrome.pl 72->| 80->| ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Verbose output option when starting daemons manually
On Fri, Nov 09, 2012 at 12:45:22AM +, "Jóhann B. Guðmundsson" wrote: > Not the first and probably not the last that expected that behavior > and proposed this. > > What's lacking is the status to be shown when units are manually > started/reloaded/restart/stopped there is just one slight problem > implementing that which is you dont want that output when the > service is started at boot time or shutdown... > > perhaps that could be solved by introducing specific boot-start and > shutdown-stop switches which would only be used to start unit or > shut down units at boot-up/shutdown > > JBG Yes, this is something I thought of, and if it is simply a flag when invoking systemctl (such as `systemctl --verbose start `), then it would not introduce anything to the boot/poweroff output. -- William Giokas | KaiSforza GnuPG Key: 0xE99A7F0F Fingerprint: F078 CFF2 45E8 1E72 6D5A 8653 CDF5 E7A5 E99A 7F0F pgppgVGI8j556.pgp Description: PGP signature ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Verbose output option when starting daemons manually
On 11/09/2012 12:23 AM, William Giokas wrote: All, I have been using systemd for a few months now, and I must say, it is a great init system. I myself am no coder, else I would attempt to write something to do just this. One not-dealbreaking thing that I do find lacking is a verbose option for `systemctl start `, essentially running `journalctl -f -u ` (and possibly for multiple dependent units as well). For most services, I feel like this would be a line or two of output just saying "It worked!" or "It broke!" but for services like netcfg@, or services that start dependencies, it could be useful to see what's getting started and how it's getting started. Again, feel free to ignore me, I don't know how feasible or practical this would be, but it seems like it would be useful. Again, sorry that I cannot put something together myself to at least show you. Thank you for your time. Not the first and probably not the last that expected that behavior and proposed this. What's lacking is the status to be shown when units are manually started/reloaded/restart/stopped there is just one slight problem implementing that which is you dont want that output when the service is started at boot time or shutdown... perhaps that could be solved by introducing specific boot-start and shutdown-stop switches which would only be used to start unit or shut down units at boot-up/shutdown JBG ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Verbose output option when starting daemons manually
All, I have been using systemd for a few months now, and I must say, it is a great init system. I myself am no coder, else I would attempt to write something to do just this. One not-dealbreaking thing that I do find lacking is a verbose option for `systemctl start `, essentially running `journalctl -f -u ` (and possibly for multiple dependent units as well). For most services, I feel like this would be a line or two of output just saying "It worked!" or "It broke!" but for services like netcfg@, or services that start dependencies, it could be useful to see what's getting started and how it's getting started. Again, feel free to ignore me, I don't know how feasible or practical this would be, but it seems like it would be useful. Again, sorry that I cannot put something together myself to at least show you. Thank you for your time. -- William Giokas | KaiSforza GnuPG Key: 0xE99A7F0F Fingerprint: F078 CFF2 45E8 1E72 6D5A 8653 CDF5 E7A5 E99A 7F0F pgphKEJ3jQMSs.pgp Description: PGP signature ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
