[prev in list] [next in list] [prev in thread] [next in thread]
List: avalon-dev
Subject: DO NOT REPLY [Bug 8649] New: -
From: bugzilla () apache ! org
Date: 2002-04-30 10:12:12
[Download RAW message or body]
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8649>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8649
Add start/stop Phoenix Scripts
Summary: Add start/stop Phoenix Scripts
Product: Avalon
Version: unspecified
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Component: Phoenix
AssignedTo: avalon-dev@jakarta.apache.org
ReportedBy: donaldp@apache.org
Expand the phoenix scripts on platforms where it is supported so that you can start
phoenix in background and also stop when it is running in background via something
like;
$PHOENIX_HOME/bin/start.sh
$PHOENIX_HOME/bin/stop.sh
Possible ways of saying shutdown include;
1. storing the process ID somewhere and sending kill message to process
2. communicating via JMX to say shutdown
3. communicating via tcp to say shutdown
4. enhancing wrapper project so that there is a java monitor process that will monitor
the "real" phoenix instance. Then we could require wrapper as part of all phoenix
installs but not require that native daemons be present
(4) is the best option.
(3) requires that we pass some sort of "key" or magic cookie between server and client process
so that the program that sends shutdown message has to have access to file in phoenix directory
(Thus offering a vague form of security)
--
To unsubscribe, e-mail: <mailto:avalon-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@jakarta.apache.org>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic