# fisheye description "Atlassian FishEye - Source control viewer" start on runlevel  stop on runlevel [!2345] kill timeout 30 env RUN_AS_USER=fisheye env BASEDIR=/opt/fisheye script LOGFILE=$BASEDIR/fisheye.out.`date +%Y-%m-%d`.log exec su - $RUN_AS_USER -c "$BASEDIR/bin/start.sh" >> $LOGFILE 2>&1 end script
The solution does not appear to be perfect, however. If I issue sudo service jira stop, I get this: jira stop/waiting. If I issue sudo service fisheye stop, I get this: stop: Unknown instance. Not good. I don't want to just kill the process when I shutdown the box. Who knows what type of data corruption will occur? I need to figure out what is wrong with my script and fix it. One difference is that the other Atlassian pieces bundle their own copy of Tomcat and that is what we invoke in the start scripts. FishEye uses something else.
I googled about Upstart and decided that I won't ever fully understand how it works. So, I've decide to make two upstart scripts. One that controls starting up FishEye and boot time (fisheye-start.conf) and one that controls shutting down FishEye during shutdown (fisheye-stop.conf). Perhaps not the most elegant solution but it appears to work. All I'm doing is calling start.sh in one and stop.sh in the other. Nothing fancy.
Custom software is the most expensive type of development due to it’s nature - unique functionality and utilization of new challenging technologies. The most important thing to understand is that java software development outsourcing is a significant decision that can have lasting ramifications for an organizationReplyDelete