[Glass] Gemstone Daemontools shutdown

Hi,

Status Version Owner Pid Port Started Type Name

------- --------- --------- ----- ----- ------------ ------ ----

OK 3.1.0.6 dario 1430 50377 mar 18 08:51 Netldi gs64ldi

OK 3.1.0.6 dario 1396 50271 mar 18 08:51 Stone gruppi

OK 3.1.0.6 dario 1398 38956 mar 18 08:50 cache gruppi~aa7c245128c6741

/etc/service/gs_seaside-9060: up (pid 30813) 1190135 seconds

/etc/service/gs_seaside-9061: up (pid 30825) 1190134 seconds

/etc/service/gs_seaside-9062: up (pid 30819) 1190135 seconds

/etc/service/gs_seaside-9063: up (pid 622) 1834134 seconds

/etc/service/gs_seaside-9064: up (pid 619) 1834134 seconds

/etc/service/gs_seaside-9065: up (pid 623) 1834134 seconds

SHUTDOWN command was received from user DataCurator session 5 gem processId 29679.

SHUTDOWN command was generated by session 5 user DataCurator .

Waiting for all tranlog writes to complete

Waiting for NetRead thread to stop

Now stopping GemStone

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass

Hi,

i have an Ubuntu 14.04 -server where i run tODE 3.1.0.6 environment with Daemontools

for start the Gemstone and relative FastCGI service as report by  gemstone_status  command:

Status Version Owner Pid Port Started Type Name

------- --------- --------- ----- ----- ------------ ------ ----

OK 3.1.0.6 dario 1430 50377 mar 18 08:51 Netldi gs64ldi

OK 3.1.0.6 dario 1396 50271 mar 18 08:51 Stone gruppi

OK 3.1.0.6 dario 1398 38956 mar 18 08:50 cache gruppi~aa7c245128c6741

/etc/service/gs_seaside-9060: up (pid 30813) 1190135 seconds

/etc/service/gs_seaside-9061: up (pid 30825) 1190134 seconds

/etc/service/gs_seaside-9062: up (pid 30819) 1190135 seconds

/etc/service/gs_seaside-9063: up (pid 622) 1834134 seconds

/etc/service/gs_seaside-9064: up (pid 619) 1834134 seconds

/etc/service/gs_seaside-9065: up (pid 623) 1834134 seconds

Now my questions is:  

when i do the shutdown command how the  Daemontools  behaves?

The stone is right shutdown ?

I am a bit fuzzy on exactly where the boundaries are between Daemontools and system startup/shutdown. Perhaps someone more familiar with Daemontools can answer?

In the relative gruppi.log  file after shutdown i found:

SHUTDOWN command was received from user DataCurator session 5 gem processId 29679.

SHUTDOWN command was generated by session 5 user DataCurator .

Waiting for all tranlog writes to complete

Waiting for NetRead thread to stop

Now stopping GemStone

I understand that it is properly terminated. Right?

The entries from the gruppi.log look familiar, but I would expect to see additional timestamps and info interspersed....
But it does look properly terminated ...

I can intercept the shutdown into Gemstone for notify  the imminent closure to the open sessions?

You don't have to intercept the notification to shutdown gems... the $GEMSTONE/bin/stopstone command by default will arrange to have any open sessions logged out ... the exception might be an interactive topaz session that is sitting logged in but idle at the command prompt ... that may cause the shutdown to wait "forever" and the topaz session will have to be terminated by you ....

Dale

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass