I am doing a series of installations of Hardy using FAI and everytime
the dhcp file gets the wrong permissions.
I added the following rules to cfengine to fix this for me on boot:
control:
AddInstallable = ( needs_networking_restarted )
files:
# hardy has the wrong permissions for this
Aargh--I am setting this to invalid. I installed rkhunter and based on
its output was able to discover that an errant script in crontab (not
part of the distribution) was damaging the permissions. Sorry!
** Changed in: ubuntu
Status: New = Invalid
--
sudo, su, and
Aargh, this happened AGAIN to me last night. I'm going to have to print
out my steps to fix it for future reference, because it kills my
networking when it occurs.
--
sudo, su, and /lib/dhcp3-client/call-dhclient-script spontaneously lost owners,
permissions
OK, this may be worse than I thought. It looks like the root group, and
perhaps in some cases setuid bits, have been lost from many files.
Here's /sbin--note that most files have lost the root group:
-rwxr-xr-x 1 root myuser 3056 2007-03-07 16:44 acpi_available
-rwxr-xr-x 1 root myuser 43204
Group ownership and setuid bits in /bin, /sbin, /boot, and all over /usr
were damaged--this isn't anything I initiated. I wrote the attached
script to repair permissions in the affected paths on my machine.
** Attachment added: recoverubuntulostpermissions.gz
This occured to me, too, when I used do-release-upgrade to upgrade from
gutsy to hardy. At the very least better error messages would be nice -
I was doing this on an EC2 instance, and when /etc/init.d/networking
created no error messages on the console whatsoever, it was very
difficult to debug.
