> I have a few Linux guests which run WebSphere.  There are times when
> applying maintenance, etc, that I need to reboot Linux on these
guests.
> If I have WebSphere auto-start during the boot process then every time
I
> boot I have to wait for WAS to finish coming up - something that takes
> several minutes - before I can even so much as sign on.  Obviously, if
I
> need to boot more than once, I end up having wasted  a lot of time.

One very simple method is to modify the startup script to check for the
presence of a "nostart" file (I've used /etc/websphere/nostart in other
places), and exit if the file is present, eg something like this
pseudocode:

if -f /etc/websphere/nostart do
    exit 0;
od

When you're done, you just rm /etc/websphere/nostart, and everything
starts normally. If you want a totally menu-driven way, use a variable
in /etc/sysconfig for that particular script, eg: 

Somewhere at the top of your startup script: 

. /etc/rc.status              (note dot space /)
. /etc/sysconfig/$0           (note dot space /)

if ($ACTIVE)!=1 then 
   exit 0;

(note pseudocode, untested...)

In /etc/sysconfig have a script named the same as the init script,
including a line like: 

# Is this script active?
ACTIVE=1

Then you can turn the script off and on using the System Configuration
editor in YaST. 

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to