topic Re: start stop scripts for application in Operating System - Linux

start stop scripts for application

Jon Gomersall — Wed, 05 Mar 2008 09:50:13 GMT

I need to start and stop an application by a specific user NOT root..

Re: start stop scripts for application

Patrick Terlisten — Wed, 05 Mar 2008 11:26:01 GMT

Hello,

try running "su $USERNAME -c $COMMAND".

Hope this helps.

Best regards,
Patrick

Re: start stop scripts for application

Ivan Ferreira — Wed, 05 Mar 2008 13:14:32 GMT

Does that means that you want that a normal user (not root) should be able to start an application? If so, use SUDO.

Re: start stop scripts for application

Jon Gomersall — Wed, 05 Mar 2008 15:09:17 GMT

I want to start an appication as a specific user when the server boots up...

Also need to shutdown the applications as the same user on system shutdown.

Re: start stop scripts for application

Ben Stokes — Wed, 05 Mar 2008 15:57:13 GMT

e.g. If your user is called jim and your application is /home/jim/application, you could add this to /etc/rc.d/rc.local:

su -c '/home/jim/application' jim &

Re: start stop scripts for application

Jared Middleton — Thu, 06 Mar 2008 00:46:33 GMT

One possible example...

/etc/init.d/myapp:
-------------
#!/bin/sh
#
# chkconfig: 235 99 10
# description: myapp Startup/Shutdown Script

case "$1" in
start)
su -c "/app/start_myapp - USERID
touch /var/lock/subsys/myapp
;;
stop)
su -c "/app/stop_myapp - USERID
rm -f /var/lock/subsys/myapp
;;
*)
echo "Usage: $0 {start|stop}"
;;
esac
-------------

Re: start stop scripts for application

Stuart Browne — Thu, 06 Mar 2008 03:08:20 GMT

You might also want to look at the 'runuser' command.

It will do basically the same thing for what you're intending, but bypasses some of the PAM checks.

If you're on a RedHat/Centos system, you might also want to use the built-in 'functions' that are available to the init.d startup/shutdown commands, in particular the 'daemon' command (with the '--user ' flag). This wraps various things and ends up calling 'runuser', but also logs it in the same fashion as all the other commands.

The 'killproc' routine however doesn't have any as-user support however.