Hi. I have a VW running on the background as a service (manually done, not by WinService package) and I've been trying to capture the shutdown signal sent when it's stopped. On development, it's not difficult. A closed event is triggered so I can simply avoid showing the dialog and add my code to the ObjectMemory>>quit. But when on a headless image it seems that the image just get closed and #quit is not being sent. Is there any way of capturing the STOP signal to perform domain specific tasks before shuting it down ? Cheers. _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
See ObjectMemory class>>registerObject: anObject
withEngineFor: purposeString. There are some comments there that claim
that some of the signals you may be interested in can be handled by the
image...
Andres. From: [hidden email] [mailto:[hidden email]] On Behalf Of Charles Johnson Sent: Monday, November 10, 2008 8:25 AM To: [hidden email] Subject: [vwnc] Capturing shutdown signal on headless image Hi.
I have a VW running on the background as a service (manually done, not by
WinService package) and I've been trying to capture the shutdown signal sent
when it's stopped.
On development, it's not difficult. A closed event is triggered so I can
simply avoid showing the dialog and add my code to the ObjectMemory>>quit.
But when on a headless image it seems that the image just get closed and #quit
is not being sent.
Is there any way of capturing the STOP signal to perform domain specific
tasks before shuting it down ?
Cheers.
_______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
In reply to this post by Charles Johnson-10
This sounds very similar to the question asked a couple of
days ago about headless shutdown on signal handling in Unix. I don't know
why it would be different between headless and headful, but it at least
appears to be in that case, and we're looking into it.
At 11:24 AM 11/10/2008, Charles Johnson wrote: Hi. --
Alan Knight [|], Engineering Manager, Cincom Smalltalk
_______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
In reply to this post by Andres Valloud-6
That seems to be it, thanks Andres. (sorry for the double post btw). Cheers. Charles. From: "Valloud, Andres" <[hidden email]> To: [hidden email] Sent: Monday, November 10, 2008 1:58:12 PM Subject: Re: [vwnc] Capturing shutdown signal on headless image See ObjectMemory class>>registerObject: anObject
withEngineFor: purposeString. There are some comments there that claim
that some of the signals you may be interested in can be handled by the
image...
Andres. From: [hidden email] [mailto:[hidden email]] On Behalf Of Charles Johnson Sent: Monday, November 10, 2008 8:25 AM To: [hidden email] Subject: [vwnc] Capturing shutdown signal on headless image Hi.
I have a VW running on the background as a service (manually done, not by
WinService package) and I've been trying to capture the shutdown signal sent
when it's stopped.
On development, it's not difficult. A closed event is triggered so I can
simply avoid showing the dialog and add my code to the ObjectMemory>>quit.
But when on a headless image it seems that the image just get closed and #quit
is not being sent.
Is there any way of capturing the STOP signal to perform domain specific
tasks before shuting it down ?
Cheers.
_______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
No problem, happy to help :).
Andres. From: [hidden email] [mailto:[hidden email]] On Behalf Of Charles Johnson Sent: Monday, November 10, 2008 1:19 PM To: [hidden email] Subject: Re: [vwnc] Capturing shutdown signal on headless image That seems to be it, thanks Andres.
(sorry for the double post btw).
Cheers.
Charles.
From: "Valloud, Andres" <[hidden email]> To: [hidden email] Sent: Monday, November 10, 2008 1:58:12 PM Subject: Re: [vwnc] Capturing shutdown signal on headless image See ObjectMemory class>>registerObject: anObject
withEngineFor: purposeString. There are some comments there that claim
that some of the signals you may be interested in can be handled by the
image...
Andres. From: [hidden email] [mailto:[hidden email]] On Behalf Of Charles Johnson Sent: Monday, November 10, 2008 8:25 AM To: [hidden email] Subject: [vwnc] Capturing shutdown signal on headless image Hi.
I have a VW running on the background as a service (manually done, not by
WinService package) and I've been trying to capture the shutdown signal sent
when it's stopped.
On development, it's not difficult. A closed event is triggered so I can
simply avoid showing the dialog and add my code to the ObjectMemory>>quit.
But when on a headless image it seems that the image just get closed and #quit
is not being sent.
Is there any way of capturing the STOP signal to perform domain specific
tasks before shuting it down ?
Cheers.
_______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
In reply to this post by Andres Valloud-6
Hi again Andres. These signals are for Unix systems, we have Windows. Now we have ObjectMemory>>registrationNames for the native OS list, but there's no description of each nor prupose object equivalence list. Assuming I'm looking for 'acceptQuitEvents', I tryed aSemaphore as prupose object and failed, tryed nil and fail and then I tryed aBlock and it failed too. Allways with 'inappropriate operation' error string. Is there any documentation I'm missing ? Cheers From: "Valloud, Andres" <[hidden email]> To: [hidden email] Sent: Monday, November 10, 2008 1:58:12 PM Subject: Re: [vwnc] Capturing shutdown signal on headless image See ObjectMemory class>>registerObject: anObject
withEngineFor: purposeString. There are some comments there that claim
that some of the signals you may be interested in can be handled by the
image...
Andres. From: [hidden email] [mailto:[hidden email]] On Behalf Of Charles Johnson Sent: Monday, November 10, 2008 8:25 AM To: [hidden email] Subject: [vwnc] Capturing shutdown signal on headless image Hi.
I have a VW running on the background as a service (manually done, not by
WinService package) and I've been trying to capture the shutdown signal sent
when it's stopped.
On development, it's not difficult. A closed event is triggered so I can
simply avoid showing the dialog and add my code to the ObjectMemory>>quit.
But when on a headless image it seems that the image just get closed and #quit
is not being sent.
Is there any way of capturing the STOP signal to perform domain specific
tasks before shuting it down ?
Cheers.
_______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Some time ago i was looking for the same, check the ServiceStartup
package published by Steve Kelly, i think it will work for you. It allows you to manage the windows service and define initialize and release methods for it. The "Startup" class comments explain wat you need to know. Hope it Helps. Emiliano. Charles Johnson escribió:. > Hi again Andres. > These signals are for Unix systems, we have Windows. > Now we have ObjectMemory>>registrationNames for the native OS list, > but there's no description of each nor prupose object equivalence list. > Assuming I'm looking for 'acceptQuitEvents', I tryed aSemaphore as > prupose object and failed, tryed nil and fail and then I tryed aBlock > and it failed too. > Allways with 'inappropriate operation' error string. > > Is there any documentation I'm missing ? > > Cheers > > ------------------------------------------------------------------------ > *From:* "Valloud, Andres" <[hidden email]> > *To:* [hidden email] > *Sent:* Monday, November 10, 2008 1:58:12 PM > *Subject:* Re: [vwnc] Capturing shutdown signal on headless image > > See ObjectMemory class>>registerObject: anObject withEngineFor: > purposeString. There are some comments there that claim that some of > the signals you may be interested in can be handled by the image... > > Andres. > > ------------------------------------------------------------------------ > *From:* [hidden email] [mailto:[hidden email]] *On > Behalf Of *Charles Johnson > *Sent:* Monday, November 10, 2008 8:25 AM > *To:* [hidden email] > *Subject:* [vwnc] Capturing shutdown signal on headless image > > Hi. > I have a VW running on the background as a service (manually done, not > by WinService package) and I've been trying to capture the shutdown > signal sent when it's stopped. > On development, it's not difficult. A closed event is triggered so I > can simply avoid showing the dialog and add my code to the > ObjectMemory>>quit. But when on a headless image it seems that the > image just get closed and #quit is not being sent. > Is there any way of capturing the STOP signal to perform domain > specific tasks before shuting it down ? > > Cheers. > > > ------------------------------------------------------------------------ > > _______________________________________________ > vwnc mailing list > [hidden email] > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
In reply to this post by Charles Johnson-10
On Tue, Nov 11, 2008 at 4:33 AM, Charles Johnson <[hidden email]> wrote:
It takes a boolean. On Windows: If true, the VM will answer false to WM_QUERYENDSESSION events sent from Windows. If false, the VM will answer true to WM_QUERYENDSESSION events sent from Windows.
The VM always tries to queue a quitSystem event when it gets sent WM_QUERYENDSESSION. The poblem is that the event is queued and so the VM cannot respond immediately. SO when acceptQuitEvents is true the VM says "No, I'm not ready to quit yet" when sent WM_QUERYENDSESSION and the VI has time to clean-up and quit. It's a hack, but the whole event queue is a hack on Windows. On Unix: If acceptQuiteEVents is true the VM will catch SIGTERM and queue a quitSystem event when it receives SIGTERM. Off the top of my head there may be a bug here in that it always catches SIGTERM, but only sends the quitSystem event when acceptQuitEvents is true. Doesn't it make more sense to not catch SIGTERM unless acceptQuitEvents is true?
HTH
_______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Free forum by Nabble | Edit this page |