I was migrating from a somewhat more relaxed laptop setup to a new one that has a few security tools on it and I had problems when macprefs was trying to chown on /Library/LaunchAgents
https://github.com/clintmod/macprefs/blob/master/startup_items.py#L45-L56
I'm able to chown the directory by hand when I omit -R and on most .plist items but anything owned by the security tools in question prevented me from doing a chown, even if it was to the same user/group it already had (root:wheel) that macprefs is trying to apply.
Makes me wonder if it is best to only chown the files that macprefs copied over? Or fail but warn, not totally bail out of macprefs, this would, however, need a file list to chown on instead of a full dir.
I was migrating from a somewhat more relaxed laptop setup to a new one that has a few security tools on it and I had problems when
macprefswas trying tochownon/Library/LaunchAgentshttps://github.com/clintmod/macprefs/blob/master/startup_items.py#L45-L56
I'm able to chown the directory by hand when I omit
-Rand on most.plistitems but anything owned by the security tools in question prevented me from doing achown, even if it was to the same user/group it already had (root:wheel) thatmacprefsis trying to apply.Makes me wonder if it is best to only
chownthe files thatmacprefscopied over? Or fail but warn, not totally bail out ofmacprefs, this would, however, need a file list to chown on instead of a full dir.