Hello all,
I *know* this is a touchy subject, so please don't turn this into yet-another-why-I-hate-systemd shouting-match. (God knows we had far too many of those lately...)
I'm in the process of upgrading a number of F14 machines to F15. (Which makes me a prime candidate for a "I survived Fedora 15" T-shirt *). In a number of these machines, the network service refuses to work preventing a clean OS boot (I'm being thrown into Emergency console; most likely udev persistent names is playing havoc with my network cards order).
So, my question is rather (?) simple: Back in old days /etc/init.d/network used to throw (semi-)informative error messages; 'systemctl start network.service' is silent and 'systemctl status network.service' returns a meaningless error code. How can I force systemctl start to dump the complete service output to the console? (Preferably without adding some boot parameters and/or configuration file editing)
Thanks, - Gilboa * Couldn't resist the urge, sorry :)
On Wed, 7 Sep 2011 01:15:07 +0300 Gilboa Davara wrote:
(Preferably without adding some boot parameters and/or configuration file editing)
There was some discussion about getting more info from systemd on the list a few weeks ago, and I seem to recall that thread mentioning a systemd config file that could be edited to log more stuff (sorry about editing the config file :-).
In fact, if I look on my system I see a bunch of log settings commented out in /etc/systemd/system.conf.
P.S. I kind of like systemd, despite all the problems, it has one really good reason to use it: It boots (my machine, anyway) a lot faster. I have parts on order for an upgrade I should be able to build this weekend, and I can't wait to see how fast it boots with a 6Gb/s sata SSD boot disk :-).
On Wed, Sep 7, 2011 at 1:30 AM, Tom Horsley horsley1953@gmail.com wrote:
On Wed, 7 Sep 2011 01:15:07 +0300 Gilboa Davara wrote:
(Preferably without adding some boot parameters and/or configuration file editing)
There was some discussion about getting more info from systemd on the list a few weeks ago, and I seem to recall that thread mentioning a systemd config file that could be edited to log more stuff (sorry about editing the config file :-).
In fact, if I look on my system I see a bunch of log settings commented out in /etc/systemd/system.conf.
Back in mid 80's there was an T.V. series called Alf (About an alien that crashed on a suburban family roof). This issue more-or-less reminds an episode in which Alf tried teaching the Tanner boy Martial arts: "Guess it only pain when you *don't* break the board... unbelievable pain" [1]
P.S. I kind of like systemd, despite all the problems, it has one really good reason to use it: It boots (my machine, anyway) a lot faster. I have parts on order for an upgrade I should be able to build this weekend, and I can't wait to see how fast it boots with a 6Gb/s sata SSD boot disk :-).
- Gilboa [1] http://www.youtube.com/watch?v=QTQ_tNNFYog 0:52.
On Wed, 7 Sep 2011 03:02:47 +0300 Gilboa Davara wrote:
- Gilboa
I always liked Alf. I had a theory that he really was an alien and they were using a sitcom to gradually introduce aliens to earth :-).
2011/9/7, Tom Horsley horsley1953@gmail.com:
P.S. I kind of like systemd, despite all the problems, it has one really good reason to use it: It boots (my machine, anyway) a lot faster. I have parts on order for an upgrade I should be able to build this weekend, and I can't wait to see how fast it boots with a 6Gb/s sata SSD boot disk :-).
Not to hijack this thread but I'm curious: is there any particular reason for you to boot so often that it matters if it's 10 secs or a 100? Unless of course neither suspend nor hibernate work.
Andras
On Wed, 7 Sep 2011 09:36:29 +0200 Andras Simon wrote:
Not to hijack this thread but I'm curious: is there any particular reason for you to boot so often that it matters if it's 10 secs or a 100? Unless of course neither suspend nor hibernate work.
Mostly doing testing. If I'm trying out f16 alpha, need to boot into it, etc. Also when applying updates, some of them often seem worth a reboot (new kernel obviously). And general impatience: People keep telling me computers are faster than humans, yet I keep wondering why I have to wait for them all the time :-).
-
Andras Simon -
Gilboa Davara -
Tom Horsley