Date: Thu, 22 Mar 2012 17:53:44 +0000 (UTC) From: "Philip M. Gollucci" <pgollucci@FreeBSD.org> To: ports-committers@FreeBSD.org, cvs-ports@FreeBSD.org, cvs-all@FreeBSD.org Subject: cvs commit: ports/sysutils/rubygem-chef Makefile ports/sysutils/rubygem-chef/files chef_client.in Message-ID: <201203221753.q2MHrihH032594@repoman.freebsd.org>
next in thread | raw e-mail | index | archive | help
pgollucci 2012-03-22 17:53:44 UTC
FreeBSD ports repository
Modified files:
sysutils/rubygem-chef Makefile
sysutils/rubygem-chef/files chef_client.in
Log:
The chef_client init script should set up the pidfile in
/var/run/chef-client.pid and instruct the chef-client process to write its PID
to this file when daemonizing. Without a pidfile, the status and onestatus
command fall back to process inspection. If chef is run with a resource defined
to :stop the chef_client service, such as chef-client::cron, then the
non-daemonized chef-client process effectivelly kills itself by running
/usr/local/etc/rc.d/chef_client status and /usr/local/etc/rc.d/chef_stop.
Run chef-client manually, then run /usr/local/etc/rc.d/chef_client onestatus.
The status will report chef-client running with the PID of the manually invoked
chef-client process.
- Bump PORTREVISION
Submitted by: Scott Sanders <ssanders@taximagic.com> (private e-mail)
Approved by: maintainer (implicit)
Feature safe: yes
Revision Changes Path
1.14 +1 -0 ports/sysutils/rubygem-chef/Makefile
1.4 +4 -2 ports/sysutils/rubygem-chef/files/chef_client.in
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201203221753.q2MHrihH032594>