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 headers it adds are SuSE-specific extentions to the sysv init scripts (were SuSE-scpecific by the time of sles 7. United-Linux-specific by the time of sles 8, and they claim to be part of LSB 1.3 . I'll have to check that). THis means that you're not supposed to touch those symlinks directly. Furthermore: you don't even give them their numbers (unlike what you'll find in many standard documentations). > > I have been creating them using pico. One advice: abandon pico ASAP. It is a horrible editor. It lacks very basic features such as "jump to line" and "undo". and can easily break long lines in config files. vi or emacs are useful tools for a sysadmins. I personally use vim (the most common vi close on linux. one with some emacs aspirations). It has syntax hilighting for half the hile formats avalable in the system (:syntax on) And there are some other editors that , while not as good as those two, are simpler for a beginner, and are better than pico. e.g. joe and nano (>= 1.0) > I have a @K01was and a @S23was to > stop and start the Websphere Application Server. No. Those two are symlinks. Where do they point to? > > When I created the start script and saved it the K01was script also changed > to look like the S23was script. -- Tzafrir Cohen +---------------------------+ http://www.technion.ac.il/~tzafrir/ |vim is a mutt's best friend| mailto:[EMAIL PROTECTED] +---------------------------+
