[Wrapper-user] Re: wrapper not trapping TERM on reboot

[Xavier T. <tx...@gm...>]

Also my init scripts stop was not being called. It appears that I need to
get a lock file in /var/lock/subsys which I can use wrapper.lockfile for
except that I run some of my services as a non root user :( so I added the
touch /var/lock/subsys/XXX in the services init script start and stop.

On 4/18/06, Xavier Toth <tx...@gm...> wrote:
>
> I'm running on Fedora Core 4 and my wrapped services aren't being stopped
> when a reboot occurs. The wrapper logs don't show TERM being caught:
> STATUS | wrapper  | 2006/04/18 14:59:02 | --> Wrapper Started as Daemon
> STATUS | wrapper  | 2006/04/18 14:59:02 | Launching a JVM...
> INFO   | jvm 1    | 2006/04/18 14:59:04 | Wrapper (Version 3.2.0)
> http://wrapper.tanukisoftware.org
> INFO   | jvm 1    | 2006/04/18 14:59:04 |
> STATUS | wrapper  | 2006/04/18 15:13:55 | --> Wrapper Started as Daemon
> STATUS | wrapper  | 2006/04/18 15:13:55 | Launching a JVM...
> INFO   | jvm 1    | 2006/04/18 15:13:57 | Wrapper (Version 3.2.0)
> http://wrapper.tanukisoftware.org
> INFO   | jvm 1    | 2006/04/18 15:13:57 |
>
> I'm not configuring wrapper.ignore_signals which defaults to false, right=
?
> As the machine reboots I see messages about removing stale pid file which
> got me looking for the problem.
>