That's how I've been doing mine. The biggest troubleshooting problem I
had, by the way, is figuring out the path. The "functions" script
located in /etc/rc.d/init.d is where the $PATH is determined at startup
time.
For example, some of my installs placed the binary files in
/usr/local/sbin. Well, the default $PATH that redhat provides doesn't
include /usr/local/sbin, though it does include /sbin and /usr/sbin. I
added /usr/local/sbin to the PATH in "functions" and everything worked
fine.
Lastly, I only recently figured out "chkconfig". Before then, I was
sort of manually changing the symbolic links in /etc/rc.d/rc[0-5].
It's not too hard if you make imaginative use of the "find" command.
Still, chkconfig makes things much easier.
=== Al
--- David Talkington <[EMAIL PROTECTED]> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
>
> Ted Gervais wrote:
>
> >But - at some point in time I would certainly like to know how to do this
> >stuff right, as RedHat would like..
>
> Ted, the fastest way to jump in is to simply copy an existing init
> script and modify it for your application. They mostly pretty much do
> the same things. You can learn a lot by reading the "functions"
> script, too.
>
> Note that if you want chkconfig to work, the "chkconfig" and
> "description" lines in each script are mandatory. You should also
> have, at a minimum, start) and stop) cases. Other than that, you can
> make them as flexible or as simple as you like.
>
> - -d
__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail.
http://personal.mail.yahoo.com/
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
