"redirecting to systemctl" not so useful

English Applications
#1

Is there any way to get the init.d scripts to tell me something useful? I understand that the output is now going to logfiles, but that’s hardly user friendly. Fine to go to logs, but should get output on console as well.

I’ve found discussions on how to fix this on Fedora, but they add “openSuSE does it different and this won’t work there.”

It seems like this must have been asked already, but couldn’t find anything on the forums. The questions I found on the forum dealt with working with specific services and confusion around what was happening, but nothing about how to fix the general problem of non-information getting echoed.

Just my 2 cents, but I hope this will be considered a bug to be fixed in 12.2.

#2

Hi
Just check the status, eg;


rclm_sensors status
redirecting to systemctl
lm_sensors.service - LSB: Load and configure hardware monitoring drivers
Loaded: loaded (/etc/init.d/lm_sensors)
Active: active (exited) since Fri, 01 Jun 2012 10:49:14
-0500; 2h 5min ago Process: 4917 ExecStart=/etc/init.d/lm_sensors start
(code=exited, status=0/SUCCESS) CGroup:
name=systemd:/system/lm_sensors.service

or

systemctl status lm_sensors.service

–
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 12.1 (x86_64) Kernel 3.1.10-1.9-desktop
up 3:48, 4 users, load average: 0.01, 0.02, 0.05
CPU Intel i5 CPU M520@2.40GHz | Intel Arrandale GPU

#3

Okay, so there’s no way to get info on the start/stop itself? The new idea is to do the action and then make a second call to see if it worked?

I guess that’s not a huge deal… still seems like less desirable behavior than the way it used to work.

#4

Hi
No, you can check on what failed etc;


systemctl --failed
systemctl --all
systemctl --help
systemd-analyze blame

It just doesn’t produce the output anymore on system start.

–
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 12.1 (x86_64) Kernel 3.1.10-1.9-desktop
up 5:21, 3 users, load average: 0.02, 0.04, 0.05
CPU Intel i5 CPU M520@2.40GHz | Intel Arrandale GPU

#5

there is no output for success, but systemd inform you on failed scripts

for ezample:


asparagus:/etc/apache2 # systemctl start apache2.service
Job failed. See system logs and 'systemctl status' for details.
asparagus:/etc/apache2 #
#6

On 2012-06-01 21:31, malcolmlewis wrote:

> It just doesn’t produce the output anymore on system start.

You can if you want.

I use “splash=verbose console=tty1 loglevel=3” without quiet, in
oS12.1. It produces a similar result as with systemV, a verbose log to
tty1 while booting. But it disappears on system login prompt.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

#7

Where are those logs? Not in /var/log/messages for sure.

Oh how I hate logs.>:( All I want is error messages IN MY FACE for interactive work!
This is the real usability problem. Totally agree with original poster.

Regarding kernel args:
My use case is: I just want to get a clue why lighttpd is failing right now. I don’t feel like rebooting (and won’t be next time either).
If I can’t debug a live production server without rebooting, that’s BAD usability.

Surely, I can add debug printouts and run it manually… No, my efforts were countered by that “redirecting to systemctl”. Head against keyboard

#8

On 2013-12-10 02:56, anordal wrote:
>
> Where are those logs? Not in /var/log/messages for sure.
>
> Oh how I hate logs.>:( All I want is error messages IN MY FACE for
> interactive work!
> This is the real usability problem. Totally agree with original poster.
>
> Regarding kernel args:
> My use case is: I just want to get a clue why lighttpd is failing right
> now. I don’t feel like rebooting (and won’t be next time either).
> If I can’t debug a live production server without rebooting, that’s BAD
> usability.
>
> Surely, I can add debug printouts and run it manually… No, my efforts
> were countered by that “redirecting to systemctl”. Head against
> keyboard

Please, open a new thread with full details of your problem. Jumping
into a thread a year old with incomplete information is counterproductive.

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)