[vwnc] Stopping headless image on Linux

> ps -ef | grep visual
>
> then
>
> kill -9 <pid>
>
> regards,
>
> David
>
> On Sat, 2008-11-08 at 17:14 +1100, Ernst wrote:
> > Hi,
> > How does one stop a headless image on Linux?
> >
> > /bin/kill  -TERM  <pid>
> > The headful VisualWorks image exits AFTER it has invoked
> > #tearDown in my subclass of UserApplication.
> > That is great because in #tearDown I save the object graph using BOSS.
> >
> > Then I save as headless:
> >  /bin/kill  -TERM  <pid>  the image does not exit
> >  /bin/kill  -KILL  <pid>   it exits but #tearDown is not invoked
> > The headless-transcript.log does not tell what happened.
> > Do I need to set up some kind of inter-process communication to stop it
> > gracefully?
> >
> > man kill
> > [...]
> > KILL       9  exit  this signal may not be blocked
> > TERM  15  exit
> >
> > Thank you
> > Ernst
> > _______________________________________________
> > vwnc mailing list
> > [hidden email]
> > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
>
> Your business, your way.
> http://sageteagroup.com

> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]] On
> Behalf Of Ernst
> Sent: 08 November 2008 08:14
> To: [hidden email]
> Subject: [vwnc] Stopping headless image on Linux
>
> Hi,
> How does one stop a headless image on Linux?
>
> /bin/kill  -TERM  <pid>
> The headful VisualWorks image exits AFTER it has invoked
> #tearDown in my subclass of UserApplication.
> That is great because in #tearDown I save the object graph using BOSS.
>
> Then I save as headless:
>  /bin/kill  -TERM  <pid>  the image does not exit
>  /bin/kill  -KILL  <pid>   it exits but #tearDown is not invoked
> The headless-transcript.log does not tell what happened.
> Do I need to set up some kind of inter-process communication to stop

> gracefully?
>
> man kill
> [...]
> KILL       9  exit  this signal may not be blocked
> TERM  15  exit
>
> Thank you
> Ernst
> _______________________________________________
> vwnc mailing list
> [hidden email]
> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

> That seems very peculiar. Unless the image is really blasted away I would
> expect subsystem actions to fire, and I wouldn't expect any difference
> between headless and headful other than which systems were active. Did the
> setUp on your system run? If you run the headless image with -gui, does it
> run? And vice versa, if you don't save headless, but merely invoke with
> -nogui?
>
> At 01:14 AM 11/8/2008, Ernst wrote:
> >Hi,
> >How does one stop a headless image on Linux?
> >
> >/bin/kill  -TERM  <pid>
> >The headful VisualWorks image exits AFTER it has invoked
> >#tearDown in my subclass of UserApplication.
> >That is great because in #tearDown I save the object graph using BOSS.
> >
> >Then I save as headless:
> > /bin/kill  -TERM  <pid>  the image does not exit
> > /bin/kill  -KILL  <pid>   it exits but #tearDown is not invoked
> >The headless-transcript.log does not tell what happened.
> >Do I need to set up some kind of inter-process communication to stop it
> >gracefully?
> >
> >man kill
> >[...]
> >KILL       9  exit  this signal may not be blocked
> >TERM  15  exit
> >
> >Thank you
> >Ernst
> >_______________________________________________
> >vwnc mailing list
> >[hidden email]
> >http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
>
> --
> Alan Knight [|], Engineering Manager, Cincom Smalltalk
> [hidden email]
> [hidden email]
> http://www.cincom.com/smalltalk

> Take a look at the ServiceStartup package in the public repository. That
> recognizes SIGUSR2, SIGTERM or SIGHUP, and can execute a block when
> receiving them. See Startup>>initializeUnixSignals. Although most of the
> package is connected with making a headless image start up as a Windows
> service (with the WinService package), the Unix signal code is only a
> few lines and hence easy to copy. Thanks to the COAST guys for their
> work!
>
> Steve
>
> > -----Original Message-----
> > From: [hidden email] [mailto:[hidden email]] On
> > Behalf Of Ernst
> > Sent: 08 November 2008 08:14
> > To: [hidden email]
> > Subject: [vwnc] Stopping headless image on Linux
> >
> > Hi,
> > How does one stop a headless image on Linux?
> >
> > /bin/kill  -TERM  <pid>
> > The headful VisualWorks image exits AFTER it has invoked
> > #tearDown in my subclass of UserApplication.
> > That is great because in #tearDown I save the object graph using BOSS.
> >
> > Then I save as headless:
> >  /bin/kill  -TERM  <pid>  the image does not exit
> >  /bin/kill  -KILL  <pid>   it exits but #tearDown is not invoked
> > The headless-transcript.log does not tell what happened.
> > Do I need to set up some kind of inter-process communication to stop
>
> it
>
> > gracefully?
> >
> > man kill
> > [...]
> > KILL       9  exit  this signal may not be blocked
> > TERM  15  exit
> >
> > Thank you
> > Ernst
> > _______________________________________________
> > vwnc mailing list
> > [hidden email]
> > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

> On Sun, 9 Nov 2008 17:14:27 +1100
>
> Ernst <[hidden email]> wrote:
> > Yes #setUp is invoked each time.
> >
> > Maybe I use the wrong VM? I change from vwlinux86gui to visual and
> > then save headless. Then try:
> > linux86/visual               work1headlessTMP.im       still same
> > linux86/visual -gui       work1headlessTMP.im       still same
> > linux86/visual -nogui  work1.im              Fatal error: No such option
> > 'n'
>
> FWIW, I run my headless images with
> visual image.im -headless
>
> i.e. -headless is an option to the image, not the VM.
>
> visual -?
> shows the VM options
>
> s.
> _______________________________________________
> vwnc mailing list
> [hidden email]
> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc