Yep, I can confirm my fix attempt isn't working properly. Just in case this may help, another scenario where something seems not to be working properly is:
[EMAIL PROTECTED]:/var/run# /etc/init.d/cherokee status cherokee web server status: Running. [EMAIL PROTECTED]:/var/run# /etc/init.d/cherokee stop Stopping web server: cherokee . [EMAIL PROTECTED]:/var/run# /etc/init.d/cherokee status cherokee web server status: Running (PID 8220), but PIDFILE not present. [EMAIL PROTECTED]:/var/run# ps uax |grep cherok root 7894 0.0 0.0 51388 2004 pts/1 S 17:33 0:00 cherokee-admin www-data 8203 0.0 0.1 190068 8988 ? Ss 17:41 0:00 php-cgi -b /tmp/cherokee-php.sock www-data 8205 0.1 0.1 190924 7788 ? S 17:41 0:00 php-cgi -b /tmp/cherokee-php.sock www-data 8206 0.0 0.0 190068 5228 ? S 17:41 0:00 php-cgi -b /tmp/cherokee-php.sock www-data 8207 0.0 0.0 190068 4436 ? S 17:41 0:00 php-cgi -b /tmp/cherokee-php.sock www-data 8208 0.0 0.0 190068 4436 ? S 17:41 0:00 php-cgi -b /tmp/cherokee-php.sock www-data 8209 0.0 0.0 190068 4436 ? S 17:41 0:00 php-cgi -b /tmp/cherokee-php.sock root 8265 0.0 0.0 6512 796 pts/1 S+ 17:44 0:00 grep cherok and php-cgi is left running. btw, this is amd64, haven't tested x86 version On Thu, Nov 6, 2008 at 5:40 PM, Alvaro Lopez Ortega <[EMAIL PROTECTED]>wrote: > On 06-nov-08, at 17:34, Antonio Pérez wrote: > > > Please, give a look to "contrib/cherokee". I think we must send > > signals to "cherokee" instead "cherokee-worker". > > > You are completely right Antonio. The init.d script ought not to send > signals to cherokee-worker, nor check its PID file. > > I haven't had time to check where the problem is, although I'm certain > that cherokee-worker has nothing to do with it. > > -- > Octality > http://www.octality.com/ > > _______________________________________________ > Cherokee mailing list > [email protected] > http://lists.octality.com/listinfo/cherokee >
_______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
