how to start and shutdown slackware faster?

NaboHipersonico · 10-19-2022, 07:29 AM

Quote:

Originally Posted by pan64

do you really need inet1 and inet2? Do you really need fuse and fuse3?

It is what I am looking at, as it says inet, I thought it was something important related to the internet and it turns out that inet1 is for windows and I imagine that inet2 too, now I will look at fuse and fuse3 and if they are not necessary I will deactivate them.

I'm going to tell you what I use slackware for, so you'll know what I need and what I don't.

Mainly what I do most is surf the internet, I surf a lot, occasionally libreoffice, play with steam, although I don't play because the electricity is very expensive, I don't use anything that I have that neither with servers nor with remote desktops.

Scan, print, view photos, let's go the typical of a home PC and nothing more. I mean play, office automation and internet.

These are the processes that are still active in the absence of surely deactivating the inet, etc:

bash-5.1# ls -lad $(find /etc/rc.d -type f -executable)
-rwxr-xr-x 1 root root 13913 feb 13 2021 /etc/rc.d/init.d/functions
-rwxr-xr-x 1 root root 1642 sep 21 17:04 /etc/rc.d/init.d/piavpn
-rwxr-xr-x 1 root root 4133 sep 23 13:55 /etc/rc.d/init.d/vboxautostart-service
-rwxr-xr-x 1 root root 6498 sep 23 13:55 /etc/rc.d/init.d/vboxballoonctrl-service
-rwxr-xr-x 1 root root 23360 sep 23 13:55 /etc/rc.d/init.d/vboxdrv
-rwxr-xr-x 1 root root 6441 sep 23 13:55 /etc/rc.d/init.d/vboxweb-service
-rwxr-xr-x 1 root root 1649 abr 24 2021 /etc/rc.d/rc.4
-rwxr-xr-x 1 root root 10077 nov 10 2021 /etc/rc.d/rc.6
-rwxr-xr-x 1 root root 552 sep 20 2021 /etc/rc.d/rc.acpid
-rwxr-xr-x 1 root root 1009 feb 13 2021 /etc/rc.d/rc.atalk
-rwxr-xr-x 1 root root 669 ene 30 2022 /etc/rc.d/rc.atd
-rwxr-xr-x 1 root root 1569 oct 6 12:47 /etc/rc.d/rc.avahidaemon
-rwxr-xr-x 1 root root 1627 oct 6 12:47 /etc/rc.d/rc.avahidnsconfd
-rwxr-xr-x 1 root root 3990 sep 24 2021 /etc/rc.d/rc.bind
-rwxr-xr-x 1 root root 3330 abr 23 2021 /etc/rc.d/rc.cpufreq
-rwxr-xr-x 1 root root 731 feb 13 2021 /etc/rc.d/rc.crond
-rwxr-xr-x 1 root root 814 sep 9 2021 /etc/rc.d/rc.dnsmasq
-rwxr-xr-x 1 root root 1579 mar 3 2021 /etc/rc.d/rc.elogind
-rwxr-xr-x 1 root root 1893 feb 13 2021 /etc/rc.d/rc.fuse
-rwxr-xr-x 1 root root 1995 sep 7 2021 /etc/rc.d/rc.fuse3
-rwxr-xr-x 1 root root 1889 oct 14 10:35 /etc/rc.d/rc.g15daemon
-rwxr-xr-x 1 root root 1153 sep 20 13:17 /etc/rc.d/rc.gpm
-rwxr-xr-x 1 root root 762 ene 9 2022 /etc/rc.d/rc.haveged
-rwxr-xr-x 1 root root 1083 dic 20 2021 /etc/rc.d/rc.httpd
-rwxr-xr-x 1 root root 29100 ene 2 2022 /etc/rc.d/rc.inet1
-rwxr-xr-x 1 root root 5340 oct 13 2019 /etc/rc.d/rc.inet2
-rwxr-xr-x 1 root root 497 feb 13 2021 /etc/rc.d/rc.inetd
-rwxr-xr-x 1 root root 3303 abr 23 2021 /etc/rc.d/rc.K
-rwxr-xr-x 1 root root 139 sep 20 13:16 /etc/rc.d/rc.keymap
-rwxr-xr-x 1 root root 629 oct 14 10:33 /etc/rc.d/rc.local
-rwxr-xr-x 1 root root 170 abr 23 2021 /etc/rc.d/rc.loop
-rwxr-xr-x 1 root root 13230 nov 12 2021 /etc/rc.d/rc.M
-rwxr-xr-x 1 root root 1950 dic 10 2021 /etc/rc.d/rc.mcelog
-rwxr-xr-x 1 root root 1864 feb 13 2021 /etc/rc.d/rc.messagebus
-rwxr-xr-x 1 root root 780 abr 23 2021 /etc/rc.d/rc.modules
-rwxr-xr-x 1 root root 691 abr 23 2021 /etc/rc.d/rc.modules.local
-rwxr-xr-x 1 root root 2674 sep 27 2021 /etc/rc.d/rc.networkmanager
-rwxr-xr-x 1 root root 805 may 21 2021 /etc/rc.d/rc.ntpd
-rwxr-xr-x 1 root root 1526 jun 6 2021 /etc/rc.d/rc.openldap
-rwxr-xr-x 1 root root 3489 feb 28 2018 /etc/rc.d/rc.openvpn
-rwxr-xr-x 1 root root 2295 may 12 2021 /etc/rc.d/rc.rpc
-rwxr-xr-x 1 root root 18050 ene 27 2022 /etc/rc.d/rc.S
-rwxr-xr-x 1 root root 1167 feb 13 2021 /etc/rc.d/rc.saslauthd
-rwxr-xr-x 1 root root 483 ene 8 2019 /etc/rc.d/rc.setterm
-rwxr-xr-x 1 root root 981 dic 21 2021 /etc/rc.d/rc.snmpd
-rwxr-xr-x 1 root root 669 dic 4 2021 /etc/rc.d/rc.syslog
-rwxr-xr-x 1 root root 1656 abr 23 2021 /etc/rc.d/rc.sysvinit
-rwxr-xr-x 1 root root 7064 abr 23 2017 /etc/rc.d/rc.udev
-rwxr-xr-x 1 root root 437 feb 13 2021 /etc/rc.d/rc.ulogd
bash-5.1#

LuckyCyborg · 10-19-2022, 07:56 AM

Quote:

Originally Posted by NaboHipersonico

It is what I am looking at, as it says inet, I thought it was something important related to the internet and it turns out that inet1 is for windows and I imagine that inet2 too, now I will look at fuse and fuse3 and if they are not necessary I will deactivate them.

Leave those scripts as executables. They are part of core logic of Slackware init system.

A clean install of Slackware should look like I've shown you previously as active init scripts.

elcore · 10-19-2022, 08:06 AM

Quote:

Originally Posted by pan64

do you really need inet1 and inet2? Do you really need fuse and fuse3?

Well, if we go down that route, one could drop them all and specify everything inside the rc.M.
This is what I did at some point :

Code:

-rwx------ 1 root root   954 Oct  2  2017 rc.4
-rwx------ 1 root root  8631 Oct  2  2017 rc.6
-rwx------ 1 root root  3103 Oct  2  2017 rc.K
-rwx------ 1 root root  5983 Feb  6  2022 rc.M
-rwx------ 1 root root 16117 Oct  2  2017 rc.S

But to expand a little on duplicates, here's a few more examples:

Do you really need both rc.atd and rc.crond since the atd manual states:

Quote:

The functionality of atd should be merged into cron

Do you really need rc.haveged since the kernel does in fact generate enough entropy now for this to become obsolete?

TBH, it's all variable, one could need a few rc scripts or none of them. I think most of us here don't use them all at the same time.

These days, I just add a few 'oneshot' things like rc.xtables, rc.font, and rc.cpufreq to this list:

Code:

-rwx------ 1 root root   552 Sep 20  2021 rc.acpid			# this is required for my desktop
-rwx------ 1 root root   669 Feb  7  2022 rc.atd			# something over here depends on this daemon
-rwx------ 1 root root   731 Feb 13  2021 rc.crond			# been using this for some timers
-rwx------ 1 root root   512 Oct  2  2017 rc.dnsmasq			# this is a must have
-rwx------ 1 root root  2577 Oct  7 08:10 rc.local			# this runs at the end of startup procedure
-rwx------ 1 root root   983 Feb  7  2022 rc.local_shutdown		# this runs at the end of shutdown procedure
-rwx------ 1 root root   168 Oct  2  2017 rc.loop			# this just loads one module, fully optional
-rwx------ 1 root root  1950 Feb  5  2022 rc.mcelog			# this is not optional for me
-rwx------ 1 root root  1864 Feb 13  2021 rc.messagebus			# this is not optional for 'firefox'
-rwx------ 1 root root   778 Oct  2  2017 rc.modules			# this loads quite a few modules here
-rwx------ 1 root root   483 Jan  8  2019 rc.setterm			# not optional for me
-rwx------ 1 root root   977 Mar  1  2021 rc.smartd			# not optional (unless you dont care about hdd health)
-rwx------ 1 root root   669 Dec  4  2021 rc.syslog			# not optional (unless you don't care about logs)
-rwx------ 1 root root  1656 Apr 23  2021 rc.sysvinit			# optional for most people, but there are quite a few packages depending on these functions
-rwx------ 1 root root  7064 Feb  5  2022 rc.udev			# this is basically optional for me, but these days it's not optional anymore unless you really want static /dev/

business_kid · 10-19-2022, 08:52 AM

Guys, Guys - there's too many good answers here.

@OP: What improvements exactly have you made? Let's hear from you with before & after timings.

NaboHipersonico · 10-19-2022, 09:05 AM

Quote:

Originally Posted by LuckyCyborg

Leave those scripts as executables. They are part of core logic of Slackware init system.

A clean install of Slackware should look like I've shown you previously as active init scripts.

Wow, I already deactivated them, but I can activate them again, which I don't know how.

To deactivate them is like this:

chmod a-x /etc/rc.d/rc.inet1

Y And to activate it, how would it be?, I have not been able to find out.

LuckyCyborg · 10-19-2022, 09:17 AM

Quote:

Originally Posted by NaboHipersonico

Wow, I already deactivated them, but I can activate them again, which I don't know how.

To deactivate them is like this:

chmod a-x /etc/rc.d/rc.inet1

Y And to activate it, how would it be?, I have not been able to find out.

It's simple

Code:

chmod a+x /etc/rc.d/rc.inet1

Please note the "plus" sign.

elcore · 10-19-2022, 09:31 AM

Quote:

Originally Posted by NaboHipersonico

I have not been able to find out.

'chmod 600 rc.script' makes rc.script -rw------- (owner can read/write)
'chmod 644 rc.script' makes rc.script -rw-r--r-- (owner can read/write, others can read)
'chmod 700 rc.script' makes rc.script -rwx------ (owner can read/write/execute)
'chmod 755 rc.script' makes rc.script -rwxr-xr-x (owner can read/write/execute, others can read/execute)

Just be careful not to accidently set write permission for other users (chmod 666 and 777), rc.whatever should only be writable by owner/root.

NaboHipersonico · 10-19-2022, 12:03 PM

Quote:

Originally Posted by elcore

'chmod 600 rc.script' makes rc.script -rw------- (owner can read/write)
'chmod 644 rc.script' makes rc.script -rw-r--r-- (owner can read/write, others can read)
'chmod 700 rc.script' makes rc.script -rwx------ (owner can read/write/execute)
'chmod 755 rc.script' makes rc.script -rwxr-xr-x (owner can read/write/execute, others can read/execute)

Just be careful not to accidently set write permission for other users (chmod 666 and 777), rc.whatever should only be writable by owner/root.

Thank you very much, I'll study it.

henca · 10-19-2022, 12:25 PM

To activate a service again you should:

Code:

chmod u+x /etc/rc.d/rc.smartd

...with smartd as an example. Even if you really don't need smartd also SSD drives has support for SMART and you will be able to read out information from them. However, you don't need smartd for reading out SMART information,

Code:

smartctl -a /dev/sda

...will work even without smartd running. With smartd running you will get log messages by syslog about your drives.

The difference between u+x and a+x is that only root will be allowed to execute scripts with u+x but any user might be able to execute a script with a+x. But even if an ordinary user is allowed to run a startup script he will probably not be able to start daemons, configure network and stuff like that.

My guess on how to get a dialog to enable or disable services is:

Code:

su
cd /
/var/log/setup/setup.services

But again, I can't promise that it works as I have messed up setup.services on my systems and can't try it myself.

regards Henrik

NaboHipersonico · 10-19-2022, 12:33 PM

Quote:

Originally Posted by LuckyCyborg

It's simple

Code:

chmod a+x /etc/rc.d/rc.inet1

Please note the "plus" sign.

Interesting I take note, because that way I can activate and deactivate.

By google I found this:

https://www.linuxtotal.com.mx/index....info_admon_003

Apparently /etc/rc.d/init.d/vboxdrv is a directory

cd /etc/rc.d/init.d/

./vboxdrv stop this stops it, but when you restart the computer it is there again, I don't know how to make it like chmod a+x /etc/rc.d/rc.fuse3, to be able to deactivate it and activate it whenever I want.

NaboHipersonico · 10-19-2022, 12:46 PM

Quote:

Originally Posted by henca

To activate a service again you should:

Code:

chmod u+x /etc/rc.d/rc.smartd

...with smartd as an example. Even if you really don't need smartd also SSD drives has support for SMART and you will be able to read out information from them. However, you don't need smartd for reading out SMART information,

Code:

smartctl -a /dev/sda

...will work even without smartd running. With smartd running you will get log messages by syslog about your drives.

The difference between u+x and a+x is that only root will be allowed to execute scripts with u+x but any user might be able to execute a script with a+x. But even if an ordinary user is allowed to run a startup script he will probably not be able to start daemons, configure network and stuff like that.

My guess on how to get a dialog to enable or disable services is:

Code:

su
cd /
/var/log/setup/setup.services

But again, I can't promise that it works as I have messed up setup.services on my systems and can't try it myself.
regards Henrik

Thank you very much, I studied everything, I did not know that smartd was also valid for ssds, if so I will activate it

GazL · 10-20-2022, 06:19 AM

There are a bunch of things in rc.M that run every boot, that don't strictly need to run every boot but only when things change.

In the past I used this patch to move them out or rc.M which saved me a good 10 - 15 seconds (on 5200rpm spinning rust. SSD users will most likely see less of a saving).

Please note: I put this here only to identify where some small savings might be made. The patch is outdated and will need updating for 15.0/current

Code:

# Patch to move some of the maintenance tasks out of rc.M
# and into their own rc file to improve boot-speed.
#
# You will probably want to run the rc.maintenance script
# from inittab. See the comments in the script for an example.
#
# Apply with:
#    cd /etc/rc.d && patch -p1 < rc.maintenance.patch
#

diff -Nurp a/rc.M b/rc.M
--- a/rc.M	2017-02-06 14:29:59.555173098 +0000
+++ b/rc.M	2017-02-06 14:29:15.925898230 +0000
@@ -77,12 +77,6 @@ if [ -x /etc/rc.d/rc.syslog -a -x /usr/s
   . /etc/rc.d/rc.syslog start
 fi
 
-# Update the X font indexes:
-if [ -x /usr/bin/fc-cache ]; then
-  echo "Updating X font indexes:  /usr/bin/fc-cache -f &"
-  /usr/bin/fc-cache -f &
-fi
-
 # Run rc.udev again.  This will start udev if it is not already running
 # (for example, upon return from runlevel 1), otherwise it will trigger it
 # to look for device changes and to generate persistent rules if needed.
@@ -163,28 +157,6 @@ if [ -x /etc/rc.d/rc.cpufreq ]; then
   . /etc/rc.d/rc.cpufreq start
 fi
 
-# Update any existing icon cache files:
-if find /usr/share/icons -maxdepth 2 2> /dev/null | grep -q icon-theme.cache ; then
-  for theme_dir in /usr/share/icons/* ; do
-    if [ -r ${theme_dir}/icon-theme.cache ]; then
-      echo "Updating icon-theme.cache in ${theme_dir}..."
-      /usr/bin/gtk-update-icon-cache -t -f ${theme_dir} 1> /dev/null 2> /dev/null &
-    fi
-  done
-  # This would be a large file and probably shouldn't be there.
-  if [ -r /usr/share/icons/icon-theme.cache ]; then
-    echo "Deleting icon-theme.cache in /usr/share/icons..."
-    #/usr/bin/gtk-update-icon-cache -t -f /usr/share/icons 1> /dev/null 2> /dev/null &
-    rm -f /usr/share/icons/icon-theme.cache
-  fi
-fi
-
-# Update mime database:
-if [ -x /usr/bin/update-mime-database -a -d /usr/share/mime ]; then
-  echo "Updating MIME database:  /usr/bin/update-mime-database /usr/share/mime &"
-  /usr/bin/update-mime-database /usr/share/mime 1> /dev/null 2> /dev/null &
-fi
-
 # Start console-kit-daemon:
 if [ -x /etc/rc.d/rc.consolekit ]; then
   sh /etc/rc.d/rc.consolekit start
@@ -201,29 +173,6 @@ if [ -x /etc/rc.d/rc.pulseaudio ]; then
   . /etc/rc.d/rc.pulseaudio start
 fi
 
-# These GTK+/pango files need to be kept up to date for
-# proper input method, pixbuf loaders, and font support.
-if [ -x /usr/bin/update-gtk-immodules ]; then
-  echo "Updating gtk.immodules:"
-  echo "  /usr/bin/update-gtk-immodules &"
-  /usr/bin/update-gtk-immodules > /dev/null 2>&1 &
-fi
-if [ -x /usr/bin/update-gdk-pixbuf-loaders ]; then
-  echo "Updating gdk-pixbuf.loaders:"
-  echo "  /usr/bin/update-gdk-pixbuf-loaders &"
-  /usr/bin/update-gdk-pixbuf-loaders > /dev/null 2>&1 &
-fi
-if [ -x /usr/bin/update-pango-querymodules ]; then
-  echo "Updating pango.modules:"
-  echo "  /usr/bin/update-pango-querymodules &"
-  /usr/bin/update-pango-querymodules > /dev/null 2>&1 &
-fi
-if [ -x /usr/bin/glib-compile-schemas ]; then
-  echo "Compiling GSettings XML schema files:"
-  echo "  /usr/bin/glib-compile-schemas /usr/share/glib-2.0/schemas &"
-  /usr/bin/glib-compile-schemas /usr/share/glib-2.0/schemas >/dev/null 2>&1 &
-fi
-
 # Start dnsmasq, a simple DHCP/DNS server:
 if [ -x /etc/rc.d/rc.dnsmasq ]; then
   /etc/rc.d/rc.dnsmasq start
diff -Nurp a/rc.maintenance b/rc.maintenance
--- a/rc.maintenance	1970-01-01 01:00:00.000000000 +0100
+++ b/rc.maintenance	2017-02-06 14:55:43.940949765 +0000
@@ -0,0 +1,31 @@
+#!/bin/sh
+#
+#  Script to run system maintenane tasks.
+#
+#  Run this script from rc.M, rc.local or add the following to your
+#  /etc/inittab to run this script in the background at system boot:
+#      # Maintenance scripts
+#      m1:34:once:/etc/rc.d/rc.maintenance
+
+exec >/var/log/maintenance.log 2>&1
+
+# Update the X font indexes:
+/usr/bin/fc-cache -v -s -f
+
+# Update any existing icon cache files:
+rm -f /usr/share/icons/icon-theme.cache
+find /usr/share/icons -maxdepth 2 -name 'icon-theme.cache' \
+  -printf '%h\0' \
+ | xargs -0r -I'{}' /usr/bin/gtk-update-icon-cache -t -f '{}'
+
+# Update mime database:
+/usr/bin/update-mime-database /usr/share/mime
+
+# These GTK+/pango files need to be kept up to date for
+# proper input method, pixbuf loaders, and font support.
+[ -x /usr/bin/update-gtk-immodule ] && /usr/bin/update-gtk-immodules --verbose
+[ -x /usr/bin/update-gdk-pixbuf-loaders ] && /usr/bin/update-gdk-pixbuf-loaders --verbose
+[ -x /usr/bin/update-pango-querymodules ] && /usr/bin/update-pango-querymodules --verbose
+[ -x /usr/bin/glib-compile-schemas ] && /usr/bin/glib-compile-schemas /usr/share/glib-2.0/schemas
+
+# All done.

Also, when comparing to systemd based systems, remember that systemd starts things on demand while Slackware starts things in advance. systemd may look like it boots faster, but the reality is that it's likely still only half-up. Ever tried to boot window and sign in the instant the login prompt shows? You end up with a non responsive desktop for 10-20 seconds, or more, because the system isn't actually fully up: it only looks like it is. The systemd situation is similar, though it happens because of the nature of the systemd design rather than an intentional attempt to deceive the user about boot speed, which is my suspicion about the Microsoft's product.

When comparing boot times, you need to make sure you're comparing like for like.

Anyway, for what it's worth...

NaboHipersonico · 10-21-2022, 05:17 AM

Quote:

Originally Posted by elcore

It sounds like network timeout to me, something you start at boot is waiting for something remote to respond..
Not aware of anything else in Slackware which adds 20sec to boot, and that machine should boot in 10sec.
In perspective, one of mine is dual core with 4G ram and it's done in 9sec from cold boot to XDM.
Post your "dmesg | tail" it might show some clue/evidence of this delay.

Hello. Sorry, at the time I did not understand about you dmesg | tail y and post you dmesg super long, this is what it gives me now that I have deactivated several things, I don't know how to interpret it, that's why I put it here.

bash-5.1$ su
Contraseña:
bash-5.1# dmesg | tail
[ 16.513044] caller _nv000720rm+0x1ad/0x200 [nvidia] mapping multiple BARs
[ 17.565893] r8169 0000:0f:00.0 eth1: Link is Up - 1Gbps/Full - flow control rx/tx
[ 17.565910] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[ 17.595143] 8021q: 802.1Q VLAN Support v1.8
[ 17.619550] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 17.622975] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 28.731590] fuse: init (API version 7.34)
[ 30.355475] logitech-hidpp-device 0003:046D:102A.0005: HID++ 1.0 device connected.
[ 131.592152] clocksource: timekeeping watchdog on CPU6: hpet wd-wd read-back delay of 71377ns
[ 131.592161] clocksource: wd-tsc-wd read-back delay of 143733ns, clock-skew test skipped!
bash-5.1#

NaboHipersonico · 10-21-2022, 05:20 AM

I see that all those who have published here have these processes activated, so they will be important, but I don't know what they are, if someone can explain it to me, because of learning. Thanks.

-rwxr-xr-x 1 root root 18050 ene 27 2022 /etc/rc.d/rc.S
-rwxr-xr-x 1 root root 13230 12 de noviembre de 2021 /etc/rc.d/rc.M
-rwxr-xr-x 1 raíz raíz 3303 23 de abril de 2021 /etc/rc.d/rc.K
-rwxr-xr-x 1 raíz raíz 1649 24 de abril de 2021 / etc/rc.d/rc.4
-rwxr-xr-x 1 raíz raíz 10077 10 de noviembre de 2021 /etc/rc.d/rc.6

NaboHipersonico · 10-21-2022, 05:24 AM

Quote:

Originally Posted by keefaz

scripts files are readable, you can find what they do just by reading the top comments
example

Code:

less /etc/rc.d/rc.atalk
# Start/stop/restart the netatalk daemon
...
(press q)

Code:

man netatalk
NETATALK(8)                         3.1.12                         NETATALK(8)

NAME
       netatalk - Netatalk AFP server service controller daemon
(press q)

I don't need running Apple File server, so

Code:

chmod -x /etc/rc.d/rc.atalk

I had not understood the first two examples, now yes, very useful to obtain information about each process. Thank you very much.