god 0.6.0 released

[Tom Werner]

This release is primarily focused on increased stability, robustness,
and code cleanliness.

The last release (0.5.0) switched from TCP sockets to Unix Domain
Sockets for the CLI tools. There were some issues regarding file
descriptors that would cause god to hang when restarting (the unix
socket was being held open by spawned processes). These problems are
all fixed in 0.6.0. You may need to kill any processes that were
started under god 0.5.0 when you upgrade to 0.6.0 (you will only need
to do this once during the upgrade process).

More attention is now paid to Syslogging behavior.

God will delete its own PID file when terminated via a user request.

A new command line option now allows you to check whether your
installation properly handles events (sometimes the C extension will
compile ok, but still not support events. Gentoo, I'm looking at you).
Run `god check` to see an attempt to use the event system. It will
tell you if your installation does not support events.

A watch can now be removed entirely at runtime using `god remove
<watch name>`.

A new condition DiskUsage allows you to check the available disk space
on a given volume.

[John Joseph Bachir]

Great, thanks Tom!


--
John Joseph Bachir
http://blog.johnjosephbachir.org
http://lyceum.ibiblio.org
http://dissent.cc
http://jjb.cc

[Blake]

Tom -

Funny you should mention the God check and event checking. I have a
cluster of Gentoo machines, a few machines running the gentoo-sources
kernel and several others running the xen-sources kernel for Xen based
virtual machines. On all the gentoo-sources machines I have been
completely unable to get the notification system working, despite it
compiling the module fine.

Any ideas what the issue is? I spent a couple of hours tweaking the
kernel two nights ago and got nowhere.

Cheers,
Blake

[Tom Werner]

I know that Ezra from Engine Yard got it working on Gentoo. I'll ask him for details and get back to you.

[Kevin Clark]

We (ezra and I) just had to modprobe the sucker (cn) if I recall.

--
Kevin Clark
http://glu.ttono.us

[Rudy Desjardins]

I had the same problem with the event stuff initially... like Kevin
and Ezra, I just had to compile & install the appropriate module then
modprobe it (add to /etc/modules.autoload.d/kernel-2.x if you don't
want to have to modprobe it every time).

[eggie5]

by what means would one upgrade? Would gem install god do the trick?

On Dec 5, 11:48 am, Tom Werner <mojo...@gmail.com> wrote:
> This release is primarily focused on increased stability, robustness,
> and code cleanliness.
>
> The last release (0.5.0) switched from TCP sockets to Unix Domain
> Sockets for the CLI tools. There were some issues regarding file
> descriptors that would cause god to hang when restarting (the unix
> socket was being held open by spawned processes). These problems are

>b all fixed in 0.6.0. You may need to kill any processes that were

[Tom Werner]

Yes, you can upgrade with `gem install god`. If you're upgrading from
0.5.0 you may need to cycle any processes that were started under god
in order to have them let go of the communications socket.

Tom

[eggie5]

Question: what's the preferred way of killing god (oh the blasphemy),
using kill or what?

[Chris Wanstrath]

On 12/6/07, eggie5 <egg...@gmail.com> wrote:
>
> Question: what's the preferred way of killing god (oh the blasphemy),
> using kill or what?

I've been using `god quit` with much success.

- Chris

[Chris Wanstrath]

But `god terminate` will kill any watches/tasks you have running in
addition to killing god.

- Chris

[car...@gmail.com]

An issue I have been having is running "god terminate" and it's
leaving the socket file, while killing the running processes. This
has been the case consistently with 0.5.0, but I have not seen it
happen yet with 0.6.0.

Clarke

[Tom Werner]

Both 0.5 and 0.6 will leave the socket file there when they close,
however 0.6 properly closes the file descriptor for spawned processes
so they don't keep a lock on socket even after god exits (thereby
preventing it from starting again). Socket behavior should be correct
in 0.6.

Tom

[car...@gmail.com]

Thanks, Tom. In 0.5 when the socket file remained and I restarted god
it would not respond to any commands, i.e. just hang when running "god
status" after restart. I would have to rm the socket and then start
god again.