> On 8/3/11, Arthur Dent wrote:
>> Wow! really useful advice! Thank You.
>> As Hiisi
says - Tip of the Day and I also agree that syslog+console
>>
should be the default.
>
> Unfortunately, systemd's
parallelization of service startup make
> output on the console
extremely ugly during boot, beca
On 8/3/11, Arthur Dent wrote:
> On Wed, 2011-08-03 at 10:32 -0700, T.C. Hollingsworth wrote:
>
>>
>> I get the same error, but it appears to be harmless; console output
>> WORKSFORME. Perhaps you're expecting output in xterm? Console ==
>> /dev/console (which usually == tty1), not the tty you ha
On Wed, 2011-08-03 at 10:32 -0700, T.C. Hollingsworth wrote:
>
> I get the same error, but it appears to be harmless; console output
> WORKSFORME. Perhaps you're expecting output in xterm? Console ==
> /dev/console (which usually == tty1), not the tty you happen to be
> running systemctl on.
On 8/3/11, Arthur Dent wrote:
> Wow! really useful advice! Thank You.
> As Hiisi says - Tip of the Day and I also agree that syslog+console
> should be the default.
Unfortunately, systemd's parallelization of service startup make
output on the console extremely ugly during boot, because several
d
On Wed, 2011-08-03 at 02:46 -0700, T.C. Hollingsworth wrote:
> On 7/22/11, Arthur Dent wrote:
> > I was really hoping that someone would reply saying something like "You
> > idiot! - Don't you know, all you need to do is to use the
> > --tellmewhatswrong switch with systemctl and all will be revea
On Wed, 2011-08-03 at 02:46 -0700, T.C. Hollingsworth wrote:
> Edit /etc/systemd/system.conf and set "DefaultStandardOutput" to one
> of "syslog", "kmsg", "kmsg+console", or "syslog+console". That will
> redirect stdout from it's default destination of /dev/null to the
> place you set. You may se
On 7/22/11, Arthur Dent wrote:
> I was really hoping that someone would reply saying something like "You
> idiot! - Don't you know, all you need to do is to use the
> --tellmewhatswrong switch with systemctl and all will be revealed!" But
> alas, no-one has said anything...
Not quite as easy as t
On Fri, 22 Jul 2011 22:26:24 +0100, Arthur Dent wrote:
> I was really hoping that someone would reply saying something like "You
> idiot! - Don't you know, all you need to do is to use the
> --tellmewhatswrong switch with systemctl and all will be revealed!" But
> alas, no-one has said anything...
On Fri, 2011-07-22 at 15:46 +, Mark Eggers wrote:
>
> This really doesn't address the lack of information that's available when
> a service fails to start using systemd. I agree that more information
> would be great.
>
> However, for Apache HTTPD, you have another tool to see what's wrong
On Fri, 22 Jul 2011 11:00:02 +0100, Arthur Dent wrote:
> Hello All,
>
> I am gradually getting used to systemd. I can now just about force my
> fingers to type "systemctl restart httpd.service" even though my brain
> is itching to write "service httpd restart" and I find this cheatsheet
> to be v
10 matches
Mail list logo
