I am somewhat of a Linux newbie. I was wondering if someone could give me some advice on the best way to add a daemon I wish to start at powerup? I compiled these daemons myself and they are not part of the SuSE distribution so they have no scripts in init.d to handle them Any advice would be greatly appreciated! Thanks, Scott
On Mon, 2006-02-06 at 14:38 -0800, Scott Stickeler wrote:
I am somewhat of a Linux newbie. I was wondering if someone could give me some advice on the best way to add a daemon I wish to start at powerup?
I compiled these daemons myself and they are not part of the SuSE distribution so they have no scripts in init.d to handle them
Any advice would be greatly appreciated!
Thanks, Scott
boot.local <commandline> followed by a "&" to launch into background. /usr/local/sbin/mydaemon -b test -c 123 & Brad Dameron SeaTab Software www.seatab.com
On Mon, 6 Feb 2006 14:38:44 -0800, you wrote:
I am somewhat of a Linux newbie. I was wondering if someone could give me some advice on the best way to add a daemon I wish to start at powerup?
I compiled these daemons myself and they are not part of the SuSE distribution so they have no scripts in init.d to handle them
Any advice would be greatly appreciated!
Thanks, Scott
Take a look in /etc/rc.d for skeleton. Rename and edit it to suit. Alternatively, you can just hack together a shell script to accept args start and stop and do whatever's appropriate. Skeleton has a boatload of bells & whistles you may or may not want to bother with. Your choice. Mike- -- If you're not confused, you're not trying hard enough. -- Please note - Due to the intense volume of spam, we have installed site-wide spam filters at catherders.com. If email from you bounces, try non-HTML, non-encoded, non-attachments,
Michael, Scott, On Monday 06 February 2006 14:49, Michael W Cocke wrote:
On Mon, 6 Feb 2006 14:38:44 -0800, you wrote:
I am somewhat of a Linux newbie. I was wondering if someone could give me some advice on the best way to add a daemon I wish to start at powerup?
...
Thanks, Scott
Take a look in /etc/rc.d for skeleton. Rename and edit it to suit.
Make that "... _copy_ and edit to suit."
...
Mike-
Randall Schulz
Thanks for all the feedback. If I choose to create a script based on skeleton what would I name it in the corresponding rc.d directory? All the files that are currently there have a letter and two numbers in the beginning of the name. -Scott On 2/6/06, Randall R Schulz <rschulz@sonic.net> wrote:
Michael, Scott,
On Monday 06 February 2006 14:49, Michael W Cocke wrote:
On Mon, 6 Feb 2006 14:38:44 -0800, you wrote:
I am somewhat of a Linux newbie. I was wondering if someone could give me some advice on the best way to add a daemon I wish to start at powerup?
...
Thanks, Scott
Take a look in /etc/rc.d for skeleton. Rename and edit it to suit.
Make that "... _copy_ and edit to suit."
...
Mike-
Randall Schulz
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Scott, On Monday 06 February 2006 15:44, Scott Stickeler wrote:
Thanks for all the feedback.
If I choose to create a script based on skeleton what would I name it in the corresponding rc.d directory? All the files that are currently there have a letter and two numbers in the beginning of the name.
Give the script a meaningful name in /etc/init.d. Use the runlevel control mechanisms available then go the YaST's runlevel control module and enable it as necessary. The symbolic links in the pertinent rc.N directories will be made for you. You should be able to figure out the information you put in the "BEGIN INIT INFO" ... "END INIT INFO" section by looking at the extensive comments in the "skeleton" script an in other working init.d scripts already present in your system.
-Scott
Randall Schulz
Great. Thanks for all the help. On 2/6/06, Randall R Schulz <rschulz@sonic.net> wrote:
Scott,
On Monday 06 February 2006 15:44, Scott Stickeler wrote:
Thanks for all the feedback.
If I choose to create a script based on skeleton what would I name it in the corresponding rc.d directory? All the files that are currently there have a letter and two numbers in the beginning of the name.
Give the script a meaningful name in /etc/init.d. Use the runlevel control mechanisms available then go the YaST's runlevel control module and enable it as necessary. The symbolic links in the pertinent rc.N directories will be made for you.
You should be able to figure out the information you put in the "BEGIN INIT INFO" ... "END INIT INFO" section by looking at the extensive comments in the "skeleton" script an in other working init.d scripts already present in your system.
-Scott
Randall Schulz
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Randall R Schulz wrote:
Give the script a meaningful name in /etc/init.d. Use the runlevel control mechanisms available then go the YaST's runlevel control module and enable it as necessary.
Or simply use "insserv <script>". /Per Jessen, Zürich
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2006-02-07 at 09:44 +0100, Per Jessen wrote:
Or simply use "insserv <script>".
Or "chkconfig script on". Makes more checks, easier to use. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFD6H4ZtTMYHG2NR9URAmK2AJ9ThYFLq7wC1lVhnO55yfQQtgLzXgCfWMT+ ijh5Au1a1jsYcqygc0e9xKY= =SBhS -----END PGP SIGNATURE-----
On 2/6/06, Scott Stickeler <sstickeler@gmail.com> wrote:
I am somewhat of a Linux newbie. I was wondering if someone could give me some advice on the best way to add a daemon I wish to start at powerup?
I compiled these daemons myself and they are not part of the SuSE distribution so they have no scripts in init.d to handle them
Any advice would be greatly appreciated!
Thanks, Scott
Look at the skeleton file in init.d and based on it create startup/stop scripts for your daemons. And then install them in the appropriate runlevels. Or, start the daemons in init.d/boot.local (just add the command as you would on a command line). That way they will be started after all other init.d scripts are started Cheers -- -- Svetoslav Milenov (Sunny)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2006-02-06 at 14:38 -0800, Scott Stickeler wrote:
I compiled these daemons myself and they are not part of the SuSE distribution so they have no scripts in init.d to handle them
Create them, using skeleton as others have said. Read "man init.d" and the chapter "The SuSE boot concept" of the SuSE admin book. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFD5/4otTMYHG2NR9URAra1AJ9IlormcJkil23ane2aFVtpf4a2MgCdH7tx riqXPuDhYT7qexnuUhTCNeA= =4MN+ -----END PGP SIGNATURE-----
participants (7)
-
Brad Dameron -
Carlos E. R. -
Michael W Cocke -
Per Jessen -
Randall R Schulz -
Scott Stickeler -
Sunny