"illegal pam.conf entry"

From Brandonhutchinson.com

(Difference between revisions)
Jump to: navigation, search
("illegal pam.conf entry")
("illegal pam.conf entry")
Line 2: Line 2:
On Solaris systems, these errors may indicate that fields in ''/etc/pam.conf'' are separated by multiple spaces instead of tabs.
On Solaris systems, these errors may indicate that fields in ''/etc/pam.conf'' are separated by multiple spaces instead of tabs.
-
Sep 16 03:15:00 hosstname cron[14629]: [ID 431104 user.crit] illegal pam.con
+
Sep 16 03:15:00 hosstname cron[14629]: [ID 431104 user.crit] illegal pam.conf entry: management: missing MODULE TYPE
-
f entry: management: missing MODULE TYPE
+
Sep 16 03:15:00 hostname cron[14629]: [ID 828992 user.crit] illegal pam.conf entry: management: missing CONTROL FLAG
-
Sep 16 03:15:00 hostname cron[14629]: [ID 828992 user.crit] illegal pam.con
+
-
f entry: management: missing CONTROL FLAG
+
Incorrect:
Incorrect:

Revision as of 20:59, 17 September 2007

"illegal pam.conf entry"

On Solaris systems, these errors may indicate that fields in /etc/pam.conf are separated by multiple spaces instead of tabs.

Sep 16 03:15:00 hosstname cron[14629]: [ID 431104 user.crit] illegal pam.conf entry: management: missing MODULE TYPE
Sep 16 03:15:00 hostname cron[14629]: [ID 828992 user.crit] illegal pam.conf entry: management: missing CONTROL FLAG

Incorrect:

$ grep -v '^#' /etc/pam.conf | cat -vet | tail -1
other   password required       pam_ldap.so.1$

Correct:

$ grep -v '^#' /etc/pam.conf | cat -vet | tail -1
other^Ipassword required^Ipam_ldap.so.1$

To fix, convert 2 or more spaces into tabs:

# perl -pi.orig -e 's/\s{2,}/\t/g' pam.conf
Personal tools