> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
> Tzafrir Cohen
> Sent: Sunday, October 19, 2003 2:41 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [LINUX-390] Creating new init scripts in init.d on SLES7
> ...
>
>
> One co
One comment
On Fri, Oct 17, 2003 at 03:10:24PM -0400, Hall, Ken (IDS ECCS) wrote:
> In SLES7, there should be symlinks for every daemon, so they all get
> run. Each script calls /etc/rc.config, which contains environment
> variables set by YAST to control which daemons actually start.
Actually, S
On Fri, Oct 17, 2003 at 02:10:35PM -0400, Terry Spaulding wrote:
> Do you have to use some special utility to create new init scripts on SLES7
> ?
less/view to read /etc/init.d/README (IIRC)
cp to copy an exiting one
$EDITOR to edit it
insserv to put it there
Note that insserv and that extra head
Ken and Dave,
Thanks for the responses. I was pretty much on the same track here once we
realized the links and files in init.d relationship and your responses
confirmed I was heading in the write direction.
I have a couple of very basic start/stop scripts working for WAS V5 on
SLES7. I need to c
the
symlinks manually. /sbin/chkconfig is a do-nothing shell script, and insserv is
broken and often destroys the symlink dependencies so badly the systems won't boot.
> -----Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
> Terry Spaulding
> Sent:
> Do you have to use some special utility to create new init
> scripts on SLES7
> ?
No. The same script is called for startup and shutdown from init via two
different symbolic links (the Sxx and Kxx links in /etc/init.d/rc/d.
That's why the start and stop sections are in the same file.
Pick up a
Do you have to use some special utility to create new init scripts on SLES7
?
I have been creating them using pico. I have a @K01was and a @S23was to
stop and start the Websphere Application Server.
When I created the start script and saved it the K01was script also changed
to look like the S23wa
