Reputation
3,445
Top tag
Next privilege 5,000 Rep.
Approve tag wiki edits
Badges
2 9 18
Impact
~321k people reached

Apr
15
accepted Puppet: how to run an exec only if puppet has made changes
Mar
4
awarded  Popular Question
Feb
11
awarded  Yearling
Aug
31
awarded  Nice Answer
Feb
11
awarded  Yearling
Sep
30
awarded  Explainer
Jul
9
comment Puppet: how to run an exec only if puppet has made changes
this sounds exactly like what i need, let me give it a try
Jul
9
comment Puppet: how to run an exec only if puppet has made changes
@MichaelHampton no i hadn't but this sounds like the perfect solution! do point me in the right direction for more info
Jul
9
comment Puppet: how to run an exec only if puppet has made changes
the point is that puppet isn't directly changing these files (its via package updates etc)
Jul
9
asked Puppet: how to run an exec only if puppet has made changes
Feb
11
awarded  Yearling
Jan
30
comment What is wrong with this iptable for Mysql Replication
why not use a maintained system like CSF - configserver.com/cp/csf.html has a web admin interface to make it easier to do
Jan
30
comment What is wrong with this iptable for Mysql Replication
why specifying source ports for remote connections, it can be safely ommited because the packets will match based on the destination ports
Jan
30
answered What is the difference between /etc/hosts.allow and denyhosts' /var/lib/denyhosts/allowed-hosts?
Jan
30
comment DirectoryIndex not being respected on AWS EC2 instance
Remember DirectoryIndex is first match, and you overrode in your htaccess - see my answer for more explanation, it might be better to clean up your config to make it more obvious
Jan
30
revised DirectoryIndex not being respected on AWS EC2 instance
added 2 characters in body
Jan
30
answered DirectoryIndex not being respected on AWS EC2 instance
Jan
30
revised Cache header for dynamically created url
added 334 characters in body
Jan
30
answered Recovery mode raid1 centos - how to?
Jan
30
comment Name resolution for internal network hostnames
can set it up however you like - most internal networks generally only have 1 resolver anyway.... you can offer it via DHCP or manually configure it per machine. if you want failback just setup a second dnsmasq instance with an identical config