From: Steve L. (JIRA) <ji...@sm...> - 2008-11-20 12:01:04
|
[ http://jira.smartfrog.org/jira/browse/SFOS-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11372#action_11372 ] Steve Loughran commented on SFOS-435: ------------------------------------- alternatively, a script that uses ps -ef to get the commands and look for smartfrog processes, find the root one and kill it > add a way to kill smartfrog using jps instead of starting smartfrog > ------------------------------------------------------------------- > > Key: SFOS-435 > URL: http://jira.smartfrog.org/jira/browse/SFOS-435 > Project: SmartFrog > Issue Type: New Feature > Components: .sfCore > Affects Versions: 3.12.000 > Environment: Java1.5 > Reporter: Steve Loughran > Assignee: Steve Loughran > Priority: Minor > > The current way to shut down smartfrog on the command line is to use sfShutdown <hostname> > on a unix system we could get away with a more brutal sfLocalShutdown which uses something like > jps -v | grep smartfrog | kill > by using the normal kill, we'd still do a clean shutdown. This approach would let anyone with the unix right permissions to shut down smartfrog, and it would be less brittle during RPM installs. > However, it gets complex once smartfrog start's spawning processes; you can't rely on a simple string, you'd need to ensure that the root process, and only the root process, gets started with a command line attribute. > IF this was the case, we could maybe bypass jps entirely, and rever to ps. Why? so that we can shut down smartfrog when there isnt enough memory to start Java, or when Java is in a mess. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.smartfrog.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |