On Aug 15, 2006, at 5:26 PM, Zack Chandler wrote: > On 8/15/06, Jason A. Hoffman <[EMAIL PROTECTED]> wrote: >> On Aug 15, 2006, at 3:55 PM, Zack Chandler wrote: >>> Hi, >>> >>> I'm in the process of moving my blog over from lighttpd -> apache >>> 2.2 >>> + mongrel. Everything works fine as long as I don't reboot :) >>> >>> On reboot apache comes up but mongrel_cluster doesn't start up the >>> pooches... >>> >>> I have added the mongrel_cluster call to my startup scripts like >>> so: >>> >>> www:/etc/init.d# update-rc.d mongrel_cluster defaults >>> Adding system startup for /etc/init.d/mongrel_cluster ... >>> /etc/rc0.d/K20mongrel_cluster -> ../init.d/mongrel_cluster >>> /etc/rc1.d/K20mongrel_cluster -> ../init.d/mongrel_cluster >>> /etc/rc6.d/K20mongrel_cluster -> ../init.d/mongrel_cluster >>> /etc/rc2.d/S20mongrel_cluster -> ../init.d/mongrel_cluster >>> /etc/rc3.d/S20mongrel_cluster -> ../init.d/mongrel_cluster >>> /etc/rc4.d/S20mongrel_cluster -> ../init.d/mongrel_cluster >>> /etc/rc5.d/S20mongrel_cluster -> ../init.d/mongrel_cluster >>> www:/etc/init.d#
You know what, looking at this the rc6.d (from what I recall, I'm a solaris/BSD person) is that run level 6 is the System reboot runtime for debian, and when something is a "K" it disables the service and keeps it stopped. 2,3,4,5 are probably all multiuser and they're "S", that's why it works from the command line once it's up. Maybe rename all the K20mongrel_cluster ones to S20mongrel_cluster. - Jason _______________________________________________ Mongrel-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/mongrel-users
