Hello:
I run a fully up-to-date Devuan ASCII installation.
Desktop environment is Xfce 4.12 with xfwm4 Window Manager.
Code:
groucho@devuan:~$ uname -ap
Linux devuan 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u4 (2018-08-21) x86_64 GNU/Linux
groucho@devuan:~$
I'm having an issue with the starting of services: they will not start.
eg:
I've ticked them in Applications -> System -> Services = [service], a pop-up for systemtoolsbackends.set asks me to authenticate and I type my root PW in.
Then I click Close but for some reason they won't start.
The services are checkroot-bootclean.sh, smartmontools and sudo.
So I try to start them from a TTY (showing just two for brevity's sake)
1. Check they are
not already running:
Code:
[root@devuan groucho]# service --status-all | grep sudo
[ ? ] alsa-utils
[ ? ] cryptdisks
[ ? ] cryptdisks-early
[ ? ] hwclock.sh
[ ? ] kmod
[ ? ] networking
[ - ] sudo
[root@devuan groucho]# service --status-all | grep smartmontools
[ ? ] alsa-utils
[ ? ] cryptdisks
[ ? ] cryptdisks-early
[ ? ] hwclock.sh
[ ? ] kmod
[ ? ] networking
[ - ] smartmontools
[root@devuan groucho]#
2. Start them as root:
Code:
[root@devuan groucho]# service sudo start
[root@devuan groucho]# service smartmontools start
3. Check if they have started:
Code:
[root@devuan groucho]# service --status-all | grep sudo
[ ? ] alsa-utils
[ ? ] cryptdisks
[ ? ] cryptdisks-early
[ ? ] hwclock.sh
[ ? ] kmod
[ ? ] networking
[ - ] sudo
[root@devuan groucho]# service --status-all | grep smartmontools
[ ? ] alsa-utils
[ ? ] cryptdisks
[ ? ] cryptdisks-early
[ ? ] hwclock.sh
[ ? ] kmod
[ ? ] networking
[ - ] smartmontools
[root@devuan groucho]#
As you can see, there's no complaints from the OS WRT my credentials or authentication.
FYI, my installation uses 'su' to get root and my user is included in the 'sudo' group.
Code:
[root@devuan groucho]# cat /etc/sudoers
#
# This file MUST be edited with the 'visudo' command as root.
#
# Please consider adding local content in /etc/sudoers.d/ instead of
# directly modifying this file.
#
# See the man page for details on how to write a sudoers file.
#
Defaults env_reset
Defaults mail_badpass
Defaults secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
# Host alias specification
# User alias specification
# Cmnd alias specification
# User privilege specification
root ALL=(ALL:ALL) ALL
# Allow members of group sudo to execute any command
%sudo ALL=(ALL:ALL) ALL
# See sudoers(5) for more information on "#include" directives:
#includedir /etc/sudoers.d
[root@devuan groucho]#
Code:
groucho@devuan:~$ groups
groucho adm dialout cdrom floppy tape sudo audio dip video plugdev netdev lpadmin scanner
groucho@devuan:~$
So, I can sudo shutdown, sudo reboot, etc. as permitted by /etc/sudoers.d/user_shutdown.
Code:
[root@devuan groucho]# cat /etc/sudoers.d/user_shutdown
groucho ALL= NOPASSWD: /usr/sbin/pm-suspend, /usr/sbin/pm-hibernate, /sbin/halt, /sbin/reboot
[root@devuan groucho]#
I can also generate a properly written (yay!) '/etc/sudoers.d/' file which will enable me to use 'sudo' for running anything (within very strict boundaries) that may I need to run and requires adm privileges.
eg: tested running LinSSID
Code:
[root@devuan groucho]# cat /etc/sudoers.d/user_linssid
%groucho ALL=(ALL) NOPASSWD:/usr/bin/linssid
[root@devuan groucho]#
So it does not seem to be an authorization issue.(?)
I was wondering if anyone using the same DE hs seen this happen or has any idea as to what could be happening with 'services'?
Thanks in advance,
A.