Hi John,<br>
<br>
What happens if you try to add the daemon via the chkconfig process ?<br>
<br>
If the script is located in /etc/rc.d/init.d<br>
<br>
You can use <br>
<br>
chkconfig --add mydaemon<br>
chkconfig --level 2 5 mydaemon on<br>
<br>
(caveat: check this syntax...I'm not near an RH/fedora box)<br>
<br>
This may produce more instructive errors than a hung GUI.<br>
<br>
HTH<br>
Andrew<br>
<br>
<br><br>
<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Date: Wed, 22 Feb 2006 21:40:07 -0600<br>From: Justin Willmert <
<a href="mailto:justin@jdjlab.com">justin@jdjlab.com</a>><br>Subject: Re: Confused about init scripts expectations<br>To: For users of Fedora Core releases <<a href="mailto:fedora-list@redhat.com">fedora-list@redhat.com
</a>><br>Message-ID: <<a href="mailto:43FD2E97.7040806@jdjlab.com">43FD2E97.7040806@jdjlab.com</a>><br>Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br><br>Mikkel L. Ellertson wrote:<br>> Jon Trauntvein wrote:
<br>><br>>> Mikkel L. Ellertson wrote:<br>>><br>>><br>>>> Jon Trauntvein wrote:<br>>>><br>>>><br>>>>> Greetings,<br>>>>><br>>>>> I am developing a daemon application to handle datalogger
<br>>>>> communications. I have developed the init script that is<br>>>>> included at the bottom of this mail based upon examples that<br>>>>> I found on the web. This script runs very<br>
>>>> well from the command line. However, when I attempt to use<br>>>>> the gnome server configuration tool to start csilgrnet, the<br>>>>> tool locks up and has to be aborted. I have searched in vain
<br>>>>> for guidelines for writing init scripts and have no idea what<br>>>>> the gui is looking for and not finding. Any assistance or<br>>>>> advise would be gratefully accepted.<br>
>>>><br>>>>> Regards,<br>>>>><br>>>>> Jon Trauntvein<br>>>>><br>>>>><br>>>> For a guide to writing them, look at the documentation for the<br>
>>> initscipts package. The file you are looking for is called<br>>>> sysvinitfiles.<br>>>><br>>>> Mikkel<br>>>><br>>> I found the above referenced file and have studied it in detail. I
<br>>> thank you.<br>>><br>>><br>>> My original problem remains, however. That is, I can execute my script<br>>> on the command line to start and stop the daemon process. If, however,<br>>> I attempt to start the daemon using the services configuration GUI
<br>>> provided by gnome, the gui will lock up and I will have to kill it to<br>>> close it. I have found, through experimentation, that, if the gui is in<br>>> this locked state, I can actually bring it out by running the script
<br>>> from the command line to shut the daemon down. The gui will then pop up<br>>> a dialogue indicating that the daemon has been started.<br>>><br>>> I am convinced that my script is finishing because I can see evidence
<br>>> that the lock file is being generated by the call to touch. Again,<br>>> there is absolutely no problem when this script is run from the command<br>>> line or when I am starting or stopping the run level.
<br>>><br>>><br>>> Regards,<br>>><br>>> Jon Trauntvein<br>>><br>>><br>> I didn't see anything wrong with it when I looked at it, but I do<br>> not use the GUI, so I could be missing something. One thing you may
<br>> want to check on is the permissions and ownership of the script.<br>><br>> Mikkel<br>><br>To go along with the permissions thing, make sure your SELinux context<br>is correct. I find that SELinux is the cause for *many* problems if you
<br>don't remember to accommodate for it.<br><br>Justin Willmert<br><br><br><br>
</blockquote></div><br>