> Sometimes tomcat does not start up after the system is booted. SuSE > SLES 9 > Linux scmlxlrf 2.6.5-7.244-s390x #1 SMP Mon Dec 12 18:32:25 UTC 2005 > s390x s390x s390x GNU/Linux > The file the S13tomcat symlink (/etc/init.d/tomcat) points to is > different (date and size) than the startup.sh file in > /usr/share/tomcat/bin. > I manually create the /etc/rc.d/rc3.d symlink to point to > /usr/share/tomcat/bin/startup.sh.
This is your problem. You need to ensure that the "standard" SuSE magic comments are included in the beginning of the startup init script you use to start it, or chkconfig (and it's evil minion insserv) will do exactly what you're observing. > Can running chkconfig delete and recreate the symlink? Not only can it, it does. Every time you run chkconfig and/or yast to install something, in fact. > Has anyone else > had this problem? It's a packaging bug, IMHO -- the startup scripts in the package should have the right magic already included. Report it to Novell. Short term fix: take the skeleton init script, paste in the startup.sh contents, and chkconfig/insserv it so that the SuSE startup process knows about it properly. That will cause the problem to not happen (until you upgrade tomcat, at which point, you can hope they've fixed it). -- db > > > > Betsie Spann > > > ---------------------------------------------------------------------- > 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 > > ---------------------------------------------------------------------- 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
