Description of problem:
When the systemd package is updated, it assumes authconfig was used to configure pam and other auth config files and executes the authconfig command in the rpm %post. This will cause problems for anyone that is not using authconfig. We use puppet to manage all of our system config, not authconfig, so updating the systemd rpm will clobber our puppet configured /etc/pam.d/system-auth and break our system configs.

Version-Release number of selected component (if applicable):
It looks like this was introduced when trying to resolve bug #679517 which made the change in systemd-20-1.fc15.

How reproducible:
Always.

Steps to Reproduce:
1. Update the systemd rpm when Fedora releases a new update.
2. The %post script in the systemd rpm will execute authconfig if /etc/pam.d/system-auth is not a symlink or /etc/pam.d/system-auth-ac does not contain the pam_systemd module.
  
Actual results:
Since we use puppet to manage /etc/pam.d/system-auth on all of our systems, our puppet configured pam is clobbered. Because we use puppet, the /etc/pam.d/system-auth config file is managed by puppet and /etc/pam.d/system-auth-ac is not used on our systems.

Expected results:
The systemd rpm should not assume that everyone uses authconfig since there are other ways to manage system config files, so authconfig should not be executed in the rpm %post if authconfig was not used to configure the system in the first place.