News for hackers. Stuff that matters.
Re:Zed Shaw completes mongrel2 manual by zrail on Friday July 30, 2010 @04:19PM (#1562465)
It's a minor point, but procer is basically exactly the tool I've been looking for. We're using runit to launch processes and getting runit to actually, you know, run has been a major pain in the ass, and it's really weird. And the c code is horrible.

Without having looked at the code, is there any way that procer could be made a standalone thing? I don't think I'll be able to get traction on mongrel2 anytime soon, but procer I could use today.

Edit: I looked at the code. Looks pretty tied into mongrel2. I might just take the ideas and run with it, though.

Re:Zed Shaw completes mongrel2 manual by zedshaw on Friday July 30, 2010 @08:18PM (#1562966)
Sure, it still needs a bit of additional features that are nice to haves, and get some testing and stuff, but it could be made as a standalone thing.

http://mongrel2.org/tktview/ff6e599f6bdb7dc63387aaad48f10f84...

There ya go.

Re:Zed Shaw completes mongrel2 manual by jamii on Friday July 30, 2010 @04:43PM (#1562555)
I was trying to get runit to work last week and it consistently broke my terminal. After calling runit nothing I typed would show up, including newline.
Re:Zed Shaw completes mongrel2 manual by zrail on Friday July 30, 2010 @05:29PM (#1562674)
The "runit" binary itself is supposed to replace init. If you want to use runit as a user-space process manager you have to use runsvdir and friends.
Re:Zed Shaw completes mongrel2 manual by jamii on Saturday July 31, 2010 @09:13AM (#1563675)
Yes, I was calling runsv and trying to bring it down again with sv. I suppose I should have been specific.