Rob van der Heij wrote: > On 5/3/06, Lee Stewart <[EMAIL PROTECTED]> wrote: > >> I'd be happy with a template! I easily accept some tailoring. But >> trying to take WAS's oddball scripts and what they return and fit that >> into the /etc/init.d/skeleton pattern can be done, but it's not for a >> novice... (And yes, David's Oracle is a help, but it's still a foreign >> language to an MVS sysprog starting with Linux...) > > No, it should not require tailoring in the code. That makes it > impossible to fix things etc. If you look at the stuff that SuSE have > done for many of their init scripts, the tweaking comes out of a > /etc/sysconfig/<service> file that is picked up by > /etc/init.d/<service> >
Here, I'm willing to share some of my own. SLES9. Still work in
progress. Ugly, I know. Had no time to furnish them further, mostly done
in 15-30 minutes.
Sorry, they don't do any exit status magic. They don't redirect stdout
and stderr to logs. Also, the nice(1) stuff is completely unimplemented
as of yet. They do handle several instances and servers where that is
appropriate: that was one of the prime reasons I wrote them. And they do
have a sysctl interface. Never tried editing with YaST2, but it should
work nicely, with possibly the only exception being adding of new
configuration fields (i.e. should it prove necessary to have more than
three instances and/or three application servers per box). Simply
copying configuration fields in *.sysconfig and fixing indexes should be
OK. Sorry, I never ran more than two instances of DB2 on the same box,
same for WAS servers (note that I don't count nodeagent as a server). :)
a) put the scripts into /etc/init.d/; simply run without arguments to
see usage; use /sbin/insserv or /sbin/chkconfig --add to manipulate
b) move the *.sysconfig files to /etc/sysconfig/* (without the
.sysconfig suffix) and edit
The scripts themselves should not require any tweaking, with the
possible exception of adding a "list" command to the scripts that also
take server index as an argument. But do look at them hard before using,
I know I wouldn't trust my system to just any script. Afterall, they
might eat it, who knows. :)
- db2das is for DB2 DAS process; there's typically only one per setup
- db2inst is for one or more DB2 instances
- rawdev is for mapping /dev/xyz to /dev/raw, but I only ever managed
to use this successfully on a pc box; hadn't installed FP11 yet to
see if it supports /dev/raw partitions
- ibmihs is simply a frontend to apachectl of IHS, does no magic
- wasdmgr is for WAS deployment manager, of course
- wasserver is for managed WAS nodes
- wasexp is for WAS express and possibly for standalone WAS servers
I did replace wasexp with wasserver just the other day when I federated
a PC with the dmgr on z/Linux. It was a drop-in thing.
Hope this helps; please send feedback. I'm willing to start a project of
some kind if there's enough interest. Enjoy the hacking.
Kind regards,
--
Grega Bremec
gregab at p0f dot net
----------------------------------------------------------------------
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
initscripts.tar.gz
Description: application/gunzip
signature.asc
Description: OpenPGP digital signature
