Re: [help-cfengine] init spawning multiple cf-execd processes at once

[Brian Bennett]

cf-execd is the scheduler that is responsible for executing the agent 
(cf-agent) at the scheduled intervals (by default 5 every minutes).

By default cf-agent will start cf-execd, cf-serverd and cf-monitord if they 
aren't running. Instead of putting cf-execd in inittab you could add a cron job 
that runs cf-agent at less frequent intervals.

To be honest though, I haven't had any problems with cf-execd crashing in quite 
some time. It's been extremely stable for me for at least the past three years.

-- 
Brian Bennett
Looking for CFEngine training?
http://www.verticalsysadmin.com/

On Jul 22, 2014, at 7:33 AM, Lorenzo Beretta lory.fu...@infinito.it wrote:

 On 07/21/2014 02:39 PM, Jimmy Thrasibule wrote:
 Hi,
 
 I've added a new line to the /etc/inittab file to monitor the CFEngine
 daemon and restart it in case this one dies.
 
 cfe:2345:respawn:/var/cfengine/bin/cf-execd
 
 The cf-execd is re-spawned as expected, except the fact that multiple
 processes are created at once.
 
 I therefore have about 20+ cf-execd processes running where I only need 1.
 
 Any idea what's causing this and how to solve it?
 
 Regards,
 Jimmy
 
 If you start things from /etc/inittab, you must make sure they do not fork; I 
 have no idea what cf-execd does, but its manpage mentions the --no-fork 
 option :)
 (If a process in inittab is spawned more than N times, init will stop 
 respawining it for a while)
 
 -- 
 You received this message because you are subscribed to the Google Groups 
 help-cfengine group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to help-cfengine+unsubscr...@googlegroups.com.
 To post to this group, send email to help-cfeng...@googlegroups.com.
 Visit this group at http://groups.google.com/group/help-cfengine.
 For more options, visit https://groups.google.com/d/optout.



smime.p7s
Description: S/MIME cryptographic signature

Understanding apt-setup

[Brian Bennett]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I'm trying to understand how apt-setup works.  Just so you know where  
I'm coming from, I have a very large install base of Debian Sarge  
built from testing installer discs.  The problem that I am having is  
that after converting my PC (my first and foremost testing box) to  
Sarge stable (I even downgraded over 100 packages to become purely  
stable) apt-setup still insists on giving me testing sources.  I've  
been building servers looking forward to the Sarge release, and now  
that it's out I want to keep them all at stable.  If we hire a new  
admin in 6 months and he uses apt-setup to get a different mirror I  
don't want it to be testing.


I've found the following in /usr/sbin/apt-setup:
# Figure out which suite to use.
if apt-cache policy | grep o=Debian,a= | grep -q  
'a=testing'; then

SUITE=testing
else
SUITE=stable
fi

The output of `apt-cache policy` is this:
$ apt-cache policy
Package Files:
100 /var/lib/dpkg/status
 release a=now
500 http://security.debian.org stable/updates/non-free Packages
 release v=3.1,o=Debian,a=stable,l=Debian-Security,c=updates/non- 
free

 origin security.debian.org
500 http://security.debian.org stable/updates/main Packages
 release v=3.1,o=Debian,a=stable,l=Debian-Security,c=updates/main
 origin security.debian.org
500 http://mirrors.kernel.org stable/non-free Packages
 release v=3.1r0,o=Debian,a=stable,l=Debian,c=non-free
 origin mirrors.kernel.org
500 http://mirrors.kernel.org stable/main Packages
 release v=3.1r0,o=Debian,a=stable,l=Debian,c=main
 origin mirrors.kernel.org
Pinned Packages:
$

As you can see, nothing says testing.  Yet when I use apt-setup it  
always creates a testing source.  How is this controlled, and how can  
this be fixed?  Should this be filed as a bug?


- -- 
Brian Bennett

[EMAIL PROTECTED]
http://digitalelf.net/

A numeric illustration uses me.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFCpdBeREYdwLXKa5IRAj3CAJ9on+k0YKuc2rnxDepw2wPEnFwOsQCgl2uD
t73Gn9u+1UIRq+FUOczpTzw=
=i63E
-END PGP SIGNATURE-


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]