DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
that is not a solution. what happens when user b of the system logs in and then shuts down the pc? the when i will login i will have to start those programms manually.
Dear Binary-dreamer!
What Yabka and NoFlag said is good, but look out: don't do both of the suggestions, becouse it is possible, that the same app will start twice, and you will have 2 running applications, which are the same (2 gaims running in the same time). When user b logs in and turns the PC off, you don't have to start the apps when you log in, becouse KDE remembers, for every user, which applications were running when you logged out, so it will start them.
You're better off with a small script, started from initd. It's quite simple, like this:
Code:
#! bin/sh
#
# script for starting program xyz at boottime
/full/path/to/application-1
/full/path/to/application-2
exit 0
Save the file with an appropiate name (like 'connectme.sh') in your home dir, make it executable with chmod +x <filename> and add a symlink to the correct rc-runlevel dir.
You're better off with a small script, started from initd. It's quite simple, like this:
Code:
#! bin/sh
#
# script for starting program xyz at boottime
/full/path/to/application-1
/full/path/to/application-2
exit 0
Save the file with an appropiate name (like 'connectme.sh') in your home dir, make it executable with chmod +x <filename> and add a symlink to the correct rc-runlevel dir.
No problem. In the rc dir's you'll find that the scripts have names starting with S and a number. This number controls the sequence of execution of the scripts. Add S20 in the symlink (ln -s <path/to/script> S20<scriptname>) so X has time to start To be sure you may increase the number to 25 or 30.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.