ssh anomaly perhaps or maybe I just dont understand

[ocpaul20]

I have some scripts in /root/Startup on my PC machine which are executed on boot by root. Stuff like mounting disks, starting mysql, nginx, and checking if they are running, etc

However, when I ssh into the PC machine from another machine (laptop) as puppy@remotehost these same root scripts execute as puppy after I have entered puppy's password. These scripts have permissions 744 in their scripts directory (so should not run as puppy) but have 777 as links in /root/Startup to this scripts directory.

Even when I login as puppy (from root) on the source laptop machine, and then ssh to the remote PC machine to puppy@remotehost I still get the ssh session executing the root/Startup scripts.

These scripts do not execute if I login as puppy on the remote host PC machine, as puppy has its own Startup directory under /home/puppy/ .

I suppose this could all happen if the ssh session logs in as root and then logs in as puppy afterwards, but I do not want the root/Startup scripts to execute. How do I achieve that please?

I am not expecting this to happen, can someone explain what is going on please?
( I dont think I am being stupid but it is always possible I have overlooked something !)

Thanks,
Paul
(Have I totally confused you all now??)

[snoring_cat]

I think you should move your startup scripts to /etc/init.d or equivalent folder. Then they will be run once on boot up, independent of user login. Things that you want run per session start could go in Startup.

On a side node. I can't recall how Puppy Linux triggers running Startup executables. I know that The Startup folder works differently depending on which Puppy version you are running.

[williams2]

I can't recall how Puppy Linux triggers running Startup executables

In /usr/sbin/delayedrun

Code: Select all

if [ -d /root/Startup ];then
 for A in /root/Startup/* ; do
  $A 2>/dev/null & 
  sleep 0.2
 done
fi

[ocpaul20]

OK thanks. Then I will move stuff to /etc/init.d and see how that goes.

[fredx181]

Even when I login as puppy (from root) on the source laptop machine, and then ssh to the remote PC machine to puppy@remotehost I still get the ssh session executing the root/Startup scripts.

The cause could be that you log in as root in the first place.
Just a guess, worth trying perhaps, make puppy the default automatic login, change this line in /etc/inittab from :
1:2345:respawn:/bin/login -f root tty6 </dev/tty1 >/dev/tty1 2>&1
to (change root to puppy):
1:2345:respawn:/bin/login -f puppy tty6 </dev/tty1 >/dev/tty1 2>&1
(and reboot, with changes saved)
Or, in case you use a login-manager, e.g. slim, set puppy to automatic login instead of root.

EDIT: Note also that DebianDog is not a true multi-user system by default, e.g. when logged in as root, you can login as puppy (enter password) (or other user) and to get back (from Desktop as puppy) as root is possible without entering password, just exit X and from console type "exit" and you are root again (and can type "startx" to get back to the Desktop as root).
With a display-manager (login-manager) installed such as slim, lightdm etc.., it's different, then it's a true multi-user system.

Fred

[ocpaul20]

I think I should move the stuff to /etc/init.d anyway, but it is good to know what I need to do to boot as puppy. Thanks.