Puppy Linux Discussion Forum

I'm running Fossapup and have done the quickpet updates. These updates are supposed to fix samba simple management (SSM) not starting after a fossapup reboot. I still have to manually turn on SSM after a reboot. Are there any other ways to have samba active after a restart, and any other options?

Thanks!!!

Randy
www.mcran.com

Warning: this is a quick and dirty method to find out where the problem is and get you up and running. It's a little geeky, but it's straight forward.

After reboot, please check in your system tray to see if your firewall is on. If it is, you might have to right click and turn it off, or change your firewall rules for access.

Next is to verify that Samba is or is not actually running. In a Terminal window, type the first line below, and verify its ouput

smbd -i

smbd version 4.12.0 started.
Copyright Andrew Tridgell and the Samba Team 1992-2020
ERROR: smbd is already running. File /var/run/smbd.pid exists and process id 28636 is running.

Here is another method to verify, with example output

ps -ef | grep "mbd -D" | grep -v grep

root     28636     1  0 10:41 ?        00:00:00 /usr/sbin/smbd -D
root     28639 28636  0 10:41 ?        00:00:00 /usr/sbin/smbd -D
root     28640 28636  0 10:41 ?        00:00:00 /usr/sbin/smbd -D
root     28641     1  0 10:41 ?        00:00:00 /usr/sbin/nmbd -D
root     28642 28636  0 10:41 ?        00:00:00 /usr/sbin/smbd -D

If it is not running, a fast fix would be to do the following to make a script that starts Samba, even after reboot

cat > /root/Startup/start_samba_manually <<EOF
#!/bin/bash
/etc/init.d/rc.samba start
EOF

chmod 755 /root/Startup/start_samba_manually

You can test to see if samba starts with this script by typing the following

/root/Startup/start_samba_manually
smbd -i

If smbd -i does show that smbd is already running, great. The script did start Samba for you. You should be able to reboot and have Samba start automatically. If it does not, then

• Check to see that there is a file called start_samba_manually in the /root/Startup folder. If not, you might not have your savefile being loaded on bootup

• Look at the Samba logs for errors. The logs should be located at /var/log/samba

There are more elegant solutions, but I think this method will get you and running the quickest. Then we can figure out why you had problems in the first place.

Thanks snoring_cat. Your fix worked for me just now on my Fossapup64 9.5. I had previously tried installing the Fossapup updates using 'quickpet' but it didn't help.
Great to have this community support.

Red