On Mon, 29 Jul 2019 05:28:26 -0000 (UTC), Markus Robert Kessler wrote:
Hi all,
during yesterday's "update" numlockd had been deactivated.
Does anyone know the reason behind?
Not me, running Mga7.
I wasn't even asked if I want this to happen.
Yeah, I used to get irritated when systemd was updated and services
were not set the way I had them before the update.
I now have a script to enable/disable the desired services.
They did it anyway, and so there's
]# ll /etc/rc.d/rc5.d/K15numlock
lrwxrwxrwx 1 root root 17 Jul 28 11:30 /etc/rc.d/rc5.d/K15numlock -> ../ init.d/numlock*
the service set to "K" like kill. Why?
I believe you may be mistaken about the /K links. You have .d/S links
to start a service during system boot, and ./K links used during
system shutdown. Those linked are also used when you issue a start/stop
service command.
Go ahead and check it out. Run this command.
locate /etc/rc.d/ | grep numlock
and you should see the Start/Kill links in each runlevel.
This is normal.
I suggest that your run systemctl status Service_Name_of_Interest_Here
any time you wish to know/verify if a status is enabled/disabled on boot
and if it is active or not.
If you want a service enabled on boot, then you need to run
systemctl enable Service_Name_Here
For example I have a /etc/rc.d/rc5.d/S29numlock and yet
$ systemctl status numlock
numlock.service - LSB: Locks NumLock key at init runlevel change
Loaded: loaded (/etc/rc.d/init.d/numlock; generated)
Active: active (exited) since Mon 2019-07-22 07:44:14 CDT; 6 days ago
Docs: man:systemd-sysv-generator(8)
Process: 851 ExecStart=/etc/rc.d/init.d/numlock start (code=exited, status=0/SUCCESS)
says it is active.
Depending on your DE (Desktop Environment), there may be a setting to
solve your problem.
PS: For you and any Lurkers
You may want to consider having your Usenet Client attach a
~/.signature file with your basic system information. That way any
subject matter expert can provide you with more explicit instructions
to use during troubleshooting or instructions to where to make what changes.
Here is a little script you can run to automagically create one with
some basic information.
----8<----8<----8<----8<--Cut/paste below this line--8<----8<----8<
#!/bin/bash #***********************************************************************
#* gen_sig_file.sh - generate $HOME/.signature file
#*
#* Automatically overwrites $HOME/.signature on each login
#* with basic information about your setup.
#* When you post to Usenet your Usenet client can append it to your
#* post which aids respondents when providing more detailed replies
#*
#*
#* Creation:
#* mkdir --parents $HOME/.local/bin
#* Save as $HOME/.local/bin/gen_sig_file.sh
#* chmod +x $HOME/.local/bin/gen_sig_file.sh
#*
#* Script Test Procedure:
#* $HOME/.local/bin/gen_sig_file.sh
#* cat $HOME/.local/bin/.signature
#*
#* Install:
#* For all users:
#* cp $HOME/.local/bin/gen_sig_file.sh /etc/profile.d
#* or put a link in /etc/profile.d back to gen_sig_file.sh
#* that everyone can read/execute.
#*
#* For just a user:
#* put $HOME/.local/bin/gen_sig_file.sh in your shell's
#* startup script, for example $HOME/.bash_profile
#*
#* Login test:
#* click up a terminal
#* su - $USER
#* cat $HOME/.local/bin/gen_sig_file.sh
#*
#* Modify your Usenet client to add/append $HOME/.signature
#* to your posts and post a message in one of the Usenet test groups
#* to verify it works as desired.
#*
#***********************************************************************
Sig_fn=$HOME/.signature
. /etc/sysconfig/desktop
set -- $(systemctl status display-manager.service | grep PID:)
Greeter=$(echo $4 | tr -d '() ')
echo -en "-- \nRunning " > $Sig_fn
cat /etc/release >> $Sig_fn
echo -e "Greeter=$Greeter DM=$DISPLAYMANAGER DE=$XDG_SESSION_DESKTOP\
on $(uname -r) $(uname -m) \n"\ >> $Sig_fn
#***********end gen_sig_file.sh ***************************
--- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)