> Hey James, can you say which version of Mongrel and which version of > mongrel_cluster you're using? The latest pre-release of both fixes a > lot of this.
Just installed 0.3.13 on FC4. The behaviour of start doesn't match what I'd expect; it doesn't complain about starting twice: [EMAIL PROTECTED] rv]$ /usr/local/bin/ruby /usr/local/bin/mongrel_rails start -d -e production -p 3000 -a 127.0.0.1 -P log/mongrel.3000.pid ** Starting Mongrel in production mode at 127.0.0.1:3000 ** Daemonizing, any open files are closed. Look at log/mongrel.3000.pid and log/mongrel.log for info. [EMAIL PROTECTED] rv]$ /usr/local/bin/ruby /usr/local/bin/mongrel_rails start -d -e production -p 3000 -a 127.0.0.1 -P log/mongrel.3000.pid ** Starting Mongrel in production mode at 127.0.0.1:3000 ** Daemonizing, any open files are closed. Look at log/mongrel.3000.pid and log/mongrel.log for info. [EMAIL PROTECTED] rv]$ My expectation would be behavior something like apachectl, where you get: [EMAIL PROTECTED] httpd-2.2.2]# /usr/local/apache2/bin/apachectl start httpd (pid 16490) already running It may be that I need to adjust my expectations and this isn't a bug, though. My preference would be to have start fail if the pid file exists, and tell you the process exists. Restart would warn about a pidfile that exists but no matching process, but would continue on to start a server. Basically, match apachectl. (I was going to say that 'start' would fail if the pidfile was there but the process was gone, just like apachectl. I checked that behavior before mailing, and that's not what happens. apachectl will happily stomp on a pidfile with a bogus pid in it, which isn't how I thought it worked.) A 'cluster::status' command (outputing maybe something easy to parse, like YAML?) of some sort would be great, too. - James _______________________________________________ Mongrel-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/mongrel-users
