Support for users of CCG software closed 7-27-20

[Labhesh <labhesh AT gmail.com>]

Hi Mark,

No worries. I might put something rough and dirty together and will share back to you guys.

Best,

Labhesh

On Mon, Mar 17, 2014 at 11:08 AM, Sammons, Mark <mssammon AT illinois.edu> wrote:

Hi, Labhesh.

At present, we don't provide a management system for component processes. The startServers.sh script is provided more as a template than a definitive solution.  Locally, we use a set of perl/shell scripts to manage processes by tracking process IDs, which sends kill signals to the relevant processes to stop them and which execute individual start-up scripts to restart them. Unfortunately., we don't yet have a good package to handle this aspect of Curator management that we can distribute.

Mark

---

From: illinois-ml-nlp-users-bounces AT cs.uiuc.edu [illinois-ml-nlp-users-bounces AT cs.uiuc.edu] on behalf of Labhesh [labhesh AT gmail.com]
Sent: Monday, March 17, 2014 12:35 PM
To: illinois-ml-nlp-users AT cs.uiuc.edu
Subject: [Illinois-ml-nlp-users] Stopping all the servers gracefully

Is there a mechanism to restart the various Curator services gracefully out of restarting the machine if everything is running on one machine?

Since all the services are being started as background services by startServers.sh, their process ids are currently not being captured. Hence, there isn't an easy way to kill the services.

Best,

Labhesh