Often (maybe 80% of the time), when I reboot a machine running Avahi, it starts using machinename-2.local as it's hostname. All the machines on my network have unique hostnames, so there is no collision.
How do I prevent Avahi from appending -2 to hostnames?
(This turns out to be an incredibly difficult thing to Google for...)
I'm running squid-deb-proxy and I want to alter the configuration using Puppet/Augeas.
When I try this:
augeas {'squid-deb-proxy.conf':
lens => 'Squid.lns',
incl => '/etc/squid-deb-proxy/squid-deb-proxy.conf',
changes => ["set http_port 3129"],
require => Package['squid-deb-proxy']
}
I get the following error from Puppet:
err: /Stage[main]/Portal::Packages::Squid-deb-proxy/Augeas[squid-deb-proxy.conf]: Could not evaluate: Save failed with return code false
I tried the following with augtool:
augtool> rm /augeas/load/*
rm : /augeas/load/* 867
augtool> set /augeas/load/Squid/lens Squid.lns
augtool> set /augeas/load/Squid/incl /etc/squid-deb-proxy/squid-deb-proxy.conf
augtool> load
augtool> print
/augeas
/augeas/root = "/"
/augeas/context = "/files"
/augeas/variables
/augeas/version = "0.10.0"
/augeas/version/save
/augeas/version/save/mode[1] = "backup"
/augeas/version/save/mode[2] = "newfile"
/augeas/version/save/mode[3] = "noop"
/augeas/version/save/mode[4] = "overwrite"
/augeas/version/defvar
/augeas/version/defvar/expr
/augeas/version/pathx
/augeas/version/pathx/functions
/augeas/version/pathx/functions/count
/augeas/version/pathx/functions/glob
/augeas/version/pathx/functions/label
/augeas/version/pathx/functions/last
/augeas/version/pathx/functions/position
/augeas/version/pathx/functions/regexp
/augeas/save = "overwrite"
/augeas/span = "disable"
/augeas/load
/augeas/load/Squid
/augeas/load/Squid/lens = "Squid.lns"
/augeas/load/Squid/incl = "/etc/squid-deb-proxy/squid-deb-proxy.conf"
/augeas/files
/augeas/files/etc
/augeas/files/etc/squid-deb-proxy
/augeas/files/etc/squid-deb-proxy/squid-deb-proxy.conf
/augeas/files/etc/squid-deb-proxy/squid-deb-proxy.conf/path = "/files/etc/squid-deb-proxy/squid-deb-proxy.conf"
/augeas/files/etc/squid-deb-proxy/squid-deb-proxy.conf/mtime = "1335175492"
/augeas/files/etc/squid-deb-proxy/squid-deb-proxy.conf/lens = "Squid.lns"
/augeas/files/etc/squid-deb-proxy/squid-deb-proxy.conf/lens/info = "/usr/share/augeas/lenses/dist/squid.aug:433.18-.95:"
/augeas/files/etc/squid-deb-proxy/squid-deb-proxy.conf/error = "parse_failed"
/augeas/files/etc/squid-deb-proxy/squid-deb-proxy.conf/error/pos = "1449"
/augeas/files/etc/squid-deb-proxy/squid-deb-proxy.conf/error/line = "42"
/augeas/files/etc/squid-deb-proxy/squid-deb-proxy.conf/error/char = "0"
/augeas/files/etc/squid-deb-proxy/squid-deb-proxy.conf/error/lens = "/usr/share/augeas/lenses/dist/squid.aug:433.18-.95:"
/augeas/files/etc/squid-deb-proxy/squid-deb-proxy.conf/error/message = "Iterated lens matched less than it should"
/files
Which seems to suggest that the lens can't parse the config file. Line 42 of squid-deb-proxy.conf reads:
cache_access_log /var/log/squid-deb-proxy/access.log
And cache_access_log doesn't appear to be listed in /usr/share/augeas/lenses/dist/squid.aug.
So... it appears to me that the Squid lens shipping with Augeas 0.10.0 doesn't cover all of the Squid configuration options. Doesn't this make the lens configurations tremendously brittle? I haven't looked into lenses, but why don't they just define the 'structure' of the file (e.g. "name whitespace value-including-spaces", or "name tabs-only value-list-space-separated", etc.)? It seems a bit strange, and a bit of a maintenance headache, to have to have the lenses know about all of the configuration options.
Have I correctly diagnosed this? And if so, what can I do about it (ideally without having to modify the lens by hand, etc.)
I'm starting to use puppet to manage a couple of servers and I'm not sure how to achieve the following.
I've got a users module which I use to create common users across all servers. I've got a git module which I use to install git and set up a system-wide config in /etc/gitconfig. What I'd like to do is:
.gitconfig into the home directories of all existing users. And obviously manage this for changes to the template..gitconfig for all future users. But I don't feel this belongs in the users module - I think it belongs in the git module. It feels like I want to know when any user has been added (not just a given instance of user), and then be able to access the parameters of that user creation (e.g. home directory, real name and username).Essentially, part 2 would be easy if I just deployed a templated .gitconfig to all users created by the users module. But I don't really want users to have a .gitconfig file if git isn't installed on the system. So what I'm really trying to say is "for all managed users on this system, if git is installed, manage a .gitconfig file".
Thanks!
I'm running wbadmin from a scheduled job, backing up my C: and D: drives to my E: and (I believe!) including the system state:
wbadmin start backup -backuptarget:e: -include:c:,d: -allCritical -noVerify -quiet
I'd like to delete old backups, but I'm concerned that all the information I can find says to use wbadmin to delete old system state backups, and vssadmin to delete other backups. As far as I know, my backups ARE system state backups, but are using VSS on E: for storage, so I'm worried about trying either of these techniques for fear of losing all my backups.
This is a home network, so I don't have a spare server to test this on.
I'm also happy to simply restrict the space used on E:, but I can't make sense of the difference between the /for and /on parameters of the relevant vssadmin command.
For reference, here's the output of vssadmin show shadows:
Contents of shadow copy set ID: {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
Contained 1 shadow copies at creation time: 07/01/2011 08:12:05
Shadow Copy ID: {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
Original Volume: (E:)\\?\Volume{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy83
Originating Machine: x.y.com
Service Machine: x.y.com
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: DataVolumeRollback
Attributes: Persistent, No auto release, No writers, Differential
[... repeated a lot...]
vssadmin show shadowstorage:
Shadow Copy Storage association
For volume: (C:)\\?\Volume{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}\
Shadow Copy Storage volume: (C:)\\?\Volume{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}\
Used Shadow Copy Storage space: 0 B
Allocated Shadow Copy Storage space: 0 B
Maximum Shadow Copy Storage space: 5.859 GB
Shadow Copy Storage association
For volume: (D:)\\?\Volume{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}\
Shadow Copy Storage volume: (D:)\\?\Volume{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}\
Used Shadow Copy Storage space: 0 B
Allocated Shadow Copy Storage space: 0 B
Maximum Shadow Copy Storage space: 40.317 GB
Shadow Copy Storage association
For volume: (E:)\\?\Volume{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}\
Shadow Copy Storage volume: (E:)\\?\Volume{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}\
Used Shadow Copy Storage space: 168.284 GB
Allocated Shadow Copy Storage space: 171.15 GB
Maximum Shadow Copy Storage space: UNBOUNDED
wbadmin get versions:
Backup time: 07/01/2011 03:00
Backup target: 1394/USB Disk labeled xxxxxxxxx(E:)
Version identifier: 01/07/2011-03:00
Can Recover: Volume(s), File(s), Application(s), Bare Metal Recovery, System State
[... repeated a lot...]