Dear Mattew, Thank you.
After including -d, script is working fine. Also, modified the script to match the original script for removing pid and lock file. I am new to linux, so if my previous doubts gave you frustration, please bear with me. Sorry for not responding you so far. After my exams, I turned to office today only. Anyway, thank you for the response. -Kavitha On Dec 20 2010, 6:33 pm, Matthew Caron <[email protected]> wrote: > On 12/20/2010 01:44 AM, kavitha wrote: > > > Answer for your question: > > Machine started tracd perfectly and just sit there. > > Hmm.. It sounds like it didn't correctly daemonize. > > What happens when you boot and start it manually? Does the terminal in > which you're starting it return to a prompt, or does it just sit there > as well? If it just sits there, then your problem is that something is > not working right with the daemon program (which is odd). > > > Solution taken: > > Trough remote, issued the below commands > > chkconfig svntracd off > > reboot > > Afer reboot issued "/etc/rc.d/init.d/svntracd start" (prints all the > > information in the console) > > What information does it print? Does it go back to a prompt. > > > > > Script modified as below: > > 1. "OPTIONS" variable changed to "OPTS" as SVN didn't accept it > > This has nothing to do with SVN. OPTIONS is used internally by that > startup script. (Or do I misunderstand?) > > > 2. Declared the "OPTS" variable as "OPTS="-p 8014 -e /home/kavitha/svn/ > > tracenv/" > > And that's likely your problem - you dropped the -d, so it's not > daemonizing. > > Also, why did you drop the -r? > > > 3. "return -1;" inside the if condition in start() throws error and > > modified into "exit;" > > Why? It will return -1 which will then exit with -1 following the > conclusion of the case statement. > > > 4. Sometimes, only lockfile is created. But stop() checks for only pid > > file, so changed the script to check for lock file also. If exist then > > remove (rm) is called for lock file also. > > I'd prefer to have it not start so I can verify that trac wasn't > manually started. Removing a lockfile from a running trac is not a good > idea. > > > Trust I have given all the information, if not please let me know. > > Nope, that's fine. > > > Did I made any wrong value in OPTS varibale? > > Yes, you left off -d. > > -d, --daemonize run in the background as a daemon > > This is also why you're not getting a pidfile: > > --pidfile=PIDFILE When daemonizing, file to which to write pid > > (implies that it won't creat a pidfile when not daemonizing). > -- > Matthew Caron > Build Engineer > Sixnet |www.sixnet.com > O +1 518 877 5173 Ext. 138 > F +1 518 602 9209 > [email protected] -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
