Paul Clayton
2006-May-26 14:32 UTC
RE: [Fedora-directory-users] /etc/init.d startup script issuesonreboot
Something rings a bell here that the DAEMON command might be your problem. I recall have some similar issue, but don''t know what I did to fix it. Does the startup script not have to be registered as an active available script. -----Original Message----- From: fedora-directory-users-bounces@redhat.com [mailto:fedora-directory-users-bounces@redhat.com] On Behalf Of Joe Sheehan Sent: 26 May 2006 04:31 PM To: fedora-directory-users@redhat.com Subject: RE: [Fedora-directory-users] /etc/init.d startup script issuesonreboot Yeah, I''m now going through the methodical approach of taking everything out of the script except the echos and then putting it back together piece by piece - just strange that using the same script via the command line would give me the same failure. Joe>From: "Paul Clayton" <Paul.Clayton@intecbilling.com> >Reply-To: "General discussion list for the Fedora Directory server >project." <fedora-directory-users@redhat.com> >To: "General discussion list for the Fedora Directory server project." ><fedora-directory-users@redhat.com> >Subject: RE: [Fedora-directory-users] /etc/init.d startup script >issuesonreboot >Date: Fri, 26 May 2006 15:28:24 +0200 > >Apologies, blonde moment here. That was what I meant. Have you thought >of simplyfing your script. Do you see any messages that your script is >being acted upon. By this I mean taking out variables and putting in >full paths to where you want to go. > >cheers > >-----Original Message----- >From: fedora-directory-users-bounces@redhat.com >[mailto:fedora-directory-users-bounces@redhat.com] On Behalf Of Joe >Sheehan >Sent: 26 May 2006 03:24 PM >To: fedora-directory-users@redhat.com >Subject: RE: [Fedora-directory-users] /etc/init.d startup script >issuesonreboot > >Little confused - do you mean in the directory >/opt/fedora-ds/slapd-''hostname'' - run ./start-slapd If so I''ve done >that and it works on command line - I still receive a failure during >reboot using that command within my startup script. Trying to get more >info out of the ldap during reboot but all I receive is a failurestatment.> > > >From: "Paul Clayton" <Paul.Clayton@intecbilling.com> > >Reply-To: "General discussion list for the Fedora Directory server > >project." <fedora-directory-users@redhat.com> > >To: "General discussion list for the Fedora Directory serverproject."> ><fedora-directory-users@redhat.com> > >Subject: RE: [Fedora-directory-users] /etc/init.d startup script > >issues > > >onreboot > >Date: Fri, 26 May 2006 13:58:51 +0200 > > > >Have tried running the command as ./slapd-`hostname` in your > >/opt/fedora_ds directory. > > > >-----Original Message----- > >From: fedora-directory-users-bounces@redhat.com > >[mailto:fedora-directory-users-bounces@redhat.com] On Behalf Of Joe > >Sheehan > >Sent: 26 May 2006 01:28 PM > >To: fedora-directory-users@redhat.com > >Subject: [Fedora-directory-users] /etc/init.d startup script issues > >on reboot > > > >We are using the startup script for Fedora as shown below with the > >corresponding /etc/sysconfig/ns-slapd The problem is during a reboot > >ns-slapd doesn''t start. (the run levels are set to 3,4,5). > > >From the command line though using this script it starts. > > > >In the /var/log/messages for a reboot we see sql_select option > >missing auxpropfunc error no mechanism available ns-slapd failed > > > >For a command line start we see > >sql_select option missing > >auxpropfunc error no mechanism available ns-slapd startedsuccessfully.> > > >Those two errors seem to be consist with a permission problem similar> >to > > > >openldap > >but we haven''t had any luck with that yet BUT is there a way to > >figure out why during a reboot it doesn''t start besides getting a > >"ns-slapd failed". > > > >Thanks (scripts below) > > > >Joe > ># Source function library. > >. /etc/init.d/functions > > > >SLAPD_HOST=`hostname -a` > >SLAPD_DIR=/opt/fedora-ds/bin/slapd/server > >PIDFILE=$SLAPD_DIR/logs/pid > >STARTPIDFILE=$SLAPD_DIR/logs/startpid > > > >if [ -f /etc/sysconfig/ns-slapd ]; then > > . /etc/sysconfig/ns-slapd > >fi > > > > > >start() { > > echo -n "Starting Fedora Directory Server: " > > if [ -f $STARTPIDFILE ]; then > > PID=`cat $STARTPIDFILE` > > echo ns-slapd already running: $PID > > exit 2; > > elif [ -f $PIDFILE ]; then > > PID=`cat $PIDFILE` > > echo ns-slapd already running: $PID > > exit 2; > > else > > echo Here we go... > > cd $SLAPD_DIR > > daemon ./ns-slapd $OPTIONS > > RETVAL=$? > > echo > > [ $RETVAL -eq 0 ] && touch /var/lock/subsys/ns-slapd > > return $RETVAL > > fi > > > >} > > > >stop() { > > echo -n "Shutting down Fedora Directory Server: " > > echo > > killproc ns-slapd > > echo > > rm -f /var/lock/subsys/ns-slapd > > return 0 > >} > > > >case "$1" in > > start) > > start > > ;; > > stop) > > stop > > ;; > > status) > > status ns-slapd > > ;; > > restart) > > stop > > start > > ;; > > *) > > echo "Usage: <servicename> {start|stop|status|restart}" > > exit 1 > > ;; > >esac > >exit $? > > > > > >-- > >Fedora-directory-users mailing list > >Fedora-directory-users@redhat.com > >https://www.redhat.com/mailman/listinfo/fedora-directory-users > >-------------------------------------------------------- > > > >This e-mail and any attachments are confidential and may also be > >legally privileged and/or copyright material of Intec Telecom Systems> >PLC (or its affiliated companies). If you are not an intended or > >authorised recipient of this e-mail or have received it in error, > >please delete it immediately and notify the sender by e-mail. In such> >a > > >case, reading, reproducing, printing or further dissemination of this> >e-mail or its contents is strictly prohibited and may be unlawful. > >Intec Telecom Systems PLC does not represent or warrant that an > >attachment hereto is free from computer viruses or other defects. The> >opinions expressed in this e-mail and any attachments may be those of> >the author and are not necessarily those of Intec Telecom SystemsPLC.> > > >-- > >Fedora-directory-users mailing list > >Fedora-directory-users@redhat.com > >https://www.redhat.com/mailman/listinfo/fedora-directory-users > > >-- >Fedora-directory-users mailing list >Fedora-directory-users@redhat.com >https://www.redhat.com/mailman/listinfo/fedora-directory-users > >-- >Fedora-directory-users mailing list >Fedora-directory-users@redhat.com >https://www.redhat.com/mailman/listinfo/fedora-directory-users-- Fedora-directory-users mailing list Fedora-directory-users@redhat.com https://www.redhat.com/mailman/listinfo/fedora-directory-users
I have a bunch of fully patched and up-to-date Solaris 2.9 machines,
using an FDS ldap server. I just converted them over from NIS, thanks to
the help from the documentation on the web site.
I can login at the command line, I can ssh to them, I thought everything
was working great.
But when I sit down in front of the console, and try to login with
dtlogin to CDE (the gui), it kicks me out.
It''s using the "other" lines from my pam.conf, which look
like this:
#
# Default definitions for Authentication management
# Used when service name is not explicitly mentioned for authentication
#
other auth requisite pam_authtok_get.so.1
other auth required pam_dhkeys.so.1
other auth binding pam_unix_auth.so.1 server_policy
other auth required pam_ldap.so.1
If I look at the log file in the FDS server ("access"), everything
looks
fine.
Has anyone else had a problem with dtlogin?
Thanks for any help,
Sam
I have this and my dtlogin works fine: # Default definitions for Authentication management # Used when service name is not explicitly mentioned for authentication # other auth requisite pam_authtok_get.so.1 other auth required pam_dhkeys.so.1 other auth required pam_unix_cred.so.1 other auth sufficient pam_unix_auth.so.1 other auth required pam_ldap.so.1 # --- Sam Smith <sam.smith@ece.gatech.edu> wrote:> I have a bunch of fully patched and up-to-date Solaris 2.9 machines, > using an FDS ldap server. I just converted them over from NIS, thanks to > the help from the documentation on the web site. > > I can login at the command line, I can ssh to them, I thought everything > was working great. > > But when I sit down in front of the console, and try to login with > dtlogin to CDE (the gui), it kicks me out. > > It''s using the "other" lines from my pam.conf, which look like this: > > # > # Default definitions for Authentication management > # Used when service name is not explicitly mentioned for authentication > # > other auth requisite pam_authtok_get.so.1 > other auth required pam_dhkeys.so.1 > other auth binding pam_unix_auth.so.1 server_policy > other auth required pam_ldap.so.1 > > If I look at the log file in the FDS server ("access"), everything looks > fine. > > Has anyone else had a problem with dtlogin? > > Thanks for any help, > Sam > > -- > Fedora-directory-users mailing list > Fedora-directory-users@redhat.com > https://www.redhat.com/mailman/listinfo/fedora-directory-users >__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Joe Sheehan
2006-May-26 15:45 UTC
RE: [Fedora-directory-users] /etc/init.d startup script issuesonreboot
Its seems to be narrowing down to the daemon command - if you can think of anything please let me know - curious why it doesn''t effect syslog etc. Joe>From: "Paul Clayton" <Paul.Clayton@intecbilling.com> >Reply-To: "General discussion list for the Fedora Directory server >project." <fedora-directory-users@redhat.com> >To: "General discussion list for the Fedora Directory server project." ><fedora-directory-users@redhat.com> >Subject: RE: [Fedora-directory-users] /etc/init.d startup script >issuesonreboot >Date: Fri, 26 May 2006 16:32:58 +0200 > >Something rings a bell here that the DAEMON command might be your >problem. I recall have some similar issue, but don''t know what I did to >fix it. Does the startup script not have to be registered as an active >available script. > >-----Original Message----- >From: fedora-directory-users-bounces@redhat.com >[mailto:fedora-directory-users-bounces@redhat.com] On Behalf Of Joe >Sheehan >Sent: 26 May 2006 04:31 PM >To: fedora-directory-users@redhat.com >Subject: RE: [Fedora-directory-users] /etc/init.d startup script >issuesonreboot > >Yeah, I''m now going through the methodical approach of taking everything >out of the script except the echos and then putting it back together >piece by piece - just strange that using the same script via the command >line would give me the same failure. > >Joe > > > >From: "Paul Clayton" <Paul.Clayton@intecbilling.com> > >Reply-To: "General discussion list for the Fedora Directory server > >project." <fedora-directory-users@redhat.com> > >To: "General discussion list for the Fedora Directory server project." > ><fedora-directory-users@redhat.com> > >Subject: RE: [Fedora-directory-users] /etc/init.d startup script > >issuesonreboot > >Date: Fri, 26 May 2006 15:28:24 +0200 > > > >Apologies, blonde moment here. That was what I meant. Have you thought > >of simplyfing your script. Do you see any messages that your script is > >being acted upon. By this I mean taking out variables and putting in > >full paths to where you want to go. > > > >cheers > > > >-----Original Message----- > >From: fedora-directory-users-bounces@redhat.com > >[mailto:fedora-directory-users-bounces@redhat.com] On Behalf Of Joe > >Sheehan > >Sent: 26 May 2006 03:24 PM > >To: fedora-directory-users@redhat.com > >Subject: RE: [Fedora-directory-users] /etc/init.d startup script > >issuesonreboot > > > >Little confused - do you mean in the directory > >/opt/fedora-ds/slapd-''hostname'' - run ./start-slapd If so I''ve done > >that and it works on command line - I still receive a failure during > >reboot using that command within my startup script. Trying to get more > >info out of the ldap during reboot but all I receive is a failure >statment. > > > > > > >From: "Paul Clayton" <Paul.Clayton@intecbilling.com> > > >Reply-To: "General discussion list for the Fedora Directory server > > >project." <fedora-directory-users@redhat.com> > > >To: "General discussion list for the Fedora Directory server >project." > > ><fedora-directory-users@redhat.com> > > >Subject: RE: [Fedora-directory-users] /etc/init.d startup script > > >issues > > > > >onreboot > > >Date: Fri, 26 May 2006 13:58:51 +0200 > > > > > >Have tried running the command as ./slapd-`hostname` in your > > >/opt/fedora_ds directory. > > > > > >-----Original Message----- > > >From: fedora-directory-users-bounces@redhat.com > > >[mailto:fedora-directory-users-bounces@redhat.com] On Behalf Of Joe > > >Sheehan > > >Sent: 26 May 2006 01:28 PM > > >To: fedora-directory-users@redhat.com > > >Subject: [Fedora-directory-users] /etc/init.d startup script issues > > >on reboot > > > > > >We are using the startup script for Fedora as shown below with the > > >corresponding /etc/sysconfig/ns-slapd The problem is during a reboot > > >ns-slapd doesn''t start. (the run levels are set to 3,4,5). > > > >From the command line though using this script it starts. > > > > > >In the /var/log/messages for a reboot we see sql_select option > > >missing auxpropfunc error no mechanism available ns-slapd failed > > > > > >For a command line start we see > > >sql_select option missing > > >auxpropfunc error no mechanism available ns-slapd started >successfully. > > > > > >Those two errors seem to be consist with a permission problem similar > > > >to > > > > > >openldap > > >but we haven''t had any luck with that yet BUT is there a way to > > >figure out why during a reboot it doesn''t start besides getting a > > >"ns-slapd failed". > > > > > >Thanks (scripts below) > > > > > >Joe > > ># Source function library. > > >. /etc/init.d/functions > > > > > >SLAPD_HOST=`hostname -a` > > >SLAPD_DIR=/opt/fedora-ds/bin/slapd/server > > >PIDFILE=$SLAPD_DIR/logs/pid > > >STARTPIDFILE=$SLAPD_DIR/logs/startpid > > > > > >if [ -f /etc/sysconfig/ns-slapd ]; then > > > . /etc/sysconfig/ns-slapd > > >fi > > > > > > > > >start() { > > > echo -n "Starting Fedora Directory Server: " > > > if [ -f $STARTPIDFILE ]; then > > > PID=`cat $STARTPIDFILE` > > > echo ns-slapd already running: $PID > > > exit 2; > > > elif [ -f $PIDFILE ]; then > > > PID=`cat $PIDFILE` > > > echo ns-slapd already running: $PID > > > exit 2; > > > else > > > echo Here we go... > > > cd $SLAPD_DIR > > > daemon ./ns-slapd $OPTIONS > > > RETVAL=$? > > > echo > > > [ $RETVAL -eq 0 ] && touch /var/lock/subsys/ns-slapd > > > return $RETVAL > > > fi > > > > > >} > > > > > >stop() { > > > echo -n "Shutting down Fedora Directory Server: " > > > echo > > > killproc ns-slapd > > > echo > > > rm -f /var/lock/subsys/ns-slapd > > > return 0 > > >} > > > > > >case "$1" in > > > start) > > > start > > > ;; > > > stop) > > > stop > > > ;; > > > status) > > > status ns-slapd > > > ;; > > > restart) > > > stop > > > start > > > ;; > > > *) > > > echo "Usage: <servicename> {start|stop|status|restart}" > > > exit 1 > > > ;; > > >esac > > >exit $? > > > > > > > > >-- > > >Fedora-directory-users mailing list > > >Fedora-directory-users@redhat.com > > >https://www.redhat.com/mailman/listinfo/fedora-directory-users > > >-------------------------------------------------------- > > > > > >This e-mail and any attachments are confidential and may also be > > >legally privileged and/or copyright material of Intec Telecom Systems > > > >PLC (or its affiliated companies). If you are not an intended or > > >authorised recipient of this e-mail or have received it in error, > > >please delete it immediately and notify the sender by e-mail. In such > > > >a > > > > >case, reading, reproducing, printing or further dissemination of this > > > >e-mail or its contents is strictly prohibited and may be unlawful. > > >Intec Telecom Systems PLC does not represent or warrant that an > > >attachment hereto is free from computer viruses or other defects. The > > > >opinions expressed in this e-mail and any attachments may be those of > > > >the author and are not necessarily those of Intec Telecom Systems >PLC. > > > > > >-- > > >Fedora-directory-users mailing list > > >Fedora-directory-users@redhat.com > > >https://www.redhat.com/mailman/listinfo/fedora-directory-users > > > > > >-- > >Fedora-directory-users mailing list > >Fedora-directory-users@redhat.com > >https://www.redhat.com/mailman/listinfo/fedora-directory-users > > > >-- > >Fedora-directory-users mailing list > >Fedora-directory-users@redhat.com > >https://www.redhat.com/mailman/listinfo/fedora-directory-users > > >-- >Fedora-directory-users mailing list >Fedora-directory-users@redhat.com >https://www.redhat.com/mailman/listinfo/fedora-directory-users > >-- >Fedora-directory-users mailing list >Fedora-directory-users@redhat.com >https://www.redhat.com/mailman/listinfo/fedora-directory-users
Joe Sheehan
2006-May-26 17:20 UTC
RE: [Fedora-directory-users] /etc/init.d startup script issuesonreboot
If within the startup script I just have /opt/fedora-ds/slapd-mysystem/start-slapd & - everything works great - once I put the daemon command back in - nothing There another system with the same problem BUT there is one system it works great on - this system is "supposedly" installed in regards to the OS, directory server etc installed the same way. If anyway, has any ideas it would be greatly appreciated. Thanks Joe>From: "Paul Clayton" <Paul.Clayton@intecbilling.com> >Reply-To: "General discussion list for the Fedora Directory server >project." <fedora-directory-users@redhat.com> >To: "General discussion list for the Fedora Directory server project." ><fedora-directory-users@redhat.com> >Subject: RE: [Fedora-directory-users] /etc/init.d startup script >issuesonreboot >Date: Fri, 26 May 2006 16:32:58 +0200 > >Something rings a bell here that the DAEMON command might be your >problem. I recall have some similar issue, but don''t know what I did to >fix it. Does the startup script not have to be registered as an active >available script. > >-----Original Message----- >From: fedora-directory-users-bounces@redhat.com >[mailto:fedora-directory-users-bounces@redhat.com] On Behalf Of Joe >Sheehan >Sent: 26 May 2006 04:31 PM >To: fedora-directory-users@redhat.com >Subject: RE: [Fedora-directory-users] /etc/init.d startup script >issuesonreboot > >Yeah, I''m now going through the methodical approach of taking everything >out of the script except the echos and then putting it back together >piece by piece - just strange that using the same script via the command >line would give me the same failure. > >Joe > > > >From: "Paul Clayton" <Paul.Clayton@intecbilling.com> > >Reply-To: "General discussion list for the Fedora Directory server > >project." <fedora-directory-users@redhat.com> > >To: "General discussion list for the Fedora Directory server project." > ><fedora-directory-users@redhat.com> > >Subject: RE: [Fedora-directory-users] /etc/init.d startup script > >issuesonreboot > >Date: Fri, 26 May 2006 15:28:24 +0200 > > > >Apologies, blonde moment here. That was what I meant. Have you thought > >of simplyfing your script. Do you see any messages that your script is > >being acted upon. By this I mean taking out variables and putting in > >full paths to where you want to go. > > > >cheers > > > >-----Original Message----- > >From: fedora-directory-users-bounces@redhat.com > >[mailto:fedora-directory-users-bounces@redhat.com] On Behalf Of Joe > >Sheehan > >Sent: 26 May 2006 03:24 PM > >To: fedora-directory-users@redhat.com > >Subject: RE: [Fedora-directory-users] /etc/init.d startup script > >issuesonreboot > > > >Little confused - do you mean in the directory > >/opt/fedora-ds/slapd-''hostname'' - run ./start-slapd If so I''ve done > >that and it works on command line - I still receive a failure during > >reboot using that command within my startup script. Trying to get more > >info out of the ldap during reboot but all I receive is a failure >statment. > > > > > > >From: "Paul Clayton" <Paul.Clayton@intecbilling.com> > > >Reply-To: "General discussion list for the Fedora Directory server > > >project." <fedora-directory-users@redhat.com> > > >To: "General discussion list for the Fedora Directory server >project." > > ><fedora-directory-users@redhat.com> > > >Subject: RE: [Fedora-directory-users] /etc/init.d startup script > > >issues > > > > >onreboot > > >Date: Fri, 26 May 2006 13:58:51 +0200 > > > > > >Have tried running the command as ./slapd-`hostname` in your > > >/opt/fedora_ds directory. > > > > > >-----Original Message----- > > >From: fedora-directory-users-bounces@redhat.com > > >[mailto:fedora-directory-users-bounces@redhat.com] On Behalf Of Joe > > >Sheehan > > >Sent: 26 May 2006 01:28 PM > > >To: fedora-directory-users@redhat.com > > >Subject: [Fedora-directory-users] /etc/init.d startup script issues > > >on reboot > > > > > >We are using the startup script for Fedora as shown below with the > > >corresponding /etc/sysconfig/ns-slapd The problem is during a reboot > > >ns-slapd doesn''t start. (the run levels are set to 3,4,5). > > > >From the command line though using this script it starts. > > > > > >In the /var/log/messages for a reboot we see sql_select option > > >missing auxpropfunc error no mechanism available ns-slapd failed > > > > > >For a command line start we see > > >sql_select option missing > > >auxpropfunc error no mechanism available ns-slapd started >successfully. > > > > > >Those two errors seem to be consist with a permission problem similar > > > >to > > > > > >openldap > > >but we haven''t had any luck with that yet BUT is there a way to > > >figure out why during a reboot it doesn''t start besides getting a > > >"ns-slapd failed". > > > > > >Thanks (scripts below) > > > > > >Joe > > ># Source function library. > > >. /etc/init.d/functions > > > > > >SLAPD_HOST=`hostname -a` > > >SLAPD_DIR=/opt/fedora-ds/bin/slapd/server > > >PIDFILE=$SLAPD_DIR/logs/pid > > >STARTPIDFILE=$SLAPD_DIR/logs/startpid > > > > > >if [ -f /etc/sysconfig/ns-slapd ]; then > > > . /etc/sysconfig/ns-slapd > > >fi > > > > > > > > >start() { > > > echo -n "Starting Fedora Directory Server: " > > > if [ -f $STARTPIDFILE ]; then > > > PID=`cat $STARTPIDFILE` > > > echo ns-slapd already running: $PID > > > exit 2; > > > elif [ -f $PIDFILE ]; then > > > PID=`cat $PIDFILE` > > > echo ns-slapd already running: $PID > > > exit 2; > > > else > > > echo Here we go... > > > cd $SLAPD_DIR > > > daemon ./ns-slapd $OPTIONS > > > RETVAL=$? > > > echo > > > [ $RETVAL -eq 0 ] && touch /var/lock/subsys/ns-slapd > > > return $RETVAL > > > fi > > > > > >} > > > > > >stop() { > > > echo -n "Shutting down Fedora Directory Server: " > > > echo > > > killproc ns-slapd > > > echo > > > rm -f /var/lock/subsys/ns-slapd > > > return 0 > > >} > > > > > >case "$1" in > > > start) > > > start > > > ;; > > > stop) > > > stop > > > ;; > > > status) > > > status ns-slapd > > > ;; > > > restart) > > > stop > > > start > > > ;; > > > *) > > > echo "Usage: <servicename> {start|stop|status|restart}" > > > exit 1 > > > ;; > > >esac > > >exit $? > > > > > > > > >-- > > >Fedora-directory-users mailing list > > >Fedora-directory-users@redhat.com > > >https://www.redhat.com/mailman/listinfo/fedora-directory-users > > >-------------------------------------------------------- > > > > > >This e-mail and any attachments are confidential and may also be > > >legally privileged and/or copyright material of Intec Telecom Systems > > > >PLC (or its affiliated companies). If you are not an intended or > > >authorised recipient of this e-mail or have received it in error, > > >please delete it immediately and notify the sender by e-mail. In such > > > >a > > > > >case, reading, reproducing, printing or further dissemination of this > > > >e-mail or its contents is strictly prohibited and may be unlawful. > > >Intec Telecom Systems PLC does not represent or warrant that an > > >attachment hereto is free from computer viruses or other defects. The > > > >opinions expressed in this e-mail and any attachments may be those of > > > >the author and are not necessarily those of Intec Telecom Systems >PLC. > > > > > >-- > > >Fedora-directory-users mailing list > > >Fedora-directory-users@redhat.com > > >https://www.redhat.com/mailman/listinfo/fedora-directory-users > > > > > >-- > >Fedora-directory-users mailing list > >Fedora-directory-users@redhat.com > >https://www.redhat.com/mailman/listinfo/fedora-directory-users > > > >-- > >Fedora-directory-users mailing list > >Fedora-directory-users@redhat.com > >https://www.redhat.com/mailman/listinfo/fedora-directory-users > > >-- >Fedora-directory-users mailing list >Fedora-directory-users@redhat.com >https://www.redhat.com/mailman/listinfo/fedora-directory-users > >-- >Fedora-directory-users mailing list >Fedora-directory-users@redhat.com >https://www.redhat.com/mailman/listinfo/fedora-directory-users
Susan wrote:>I have this and my dtlogin works fine: > > ># Default definitions for Authentication management ># Used when service name is not explicitly mentioned for authentication ># >other auth requisite pam_authtok_get.so.1 >other auth required pam_dhkeys.so.1 >other auth required pam_unix_cred.so.1 >other auth sufficient pam_unix_auth.so.1 >other auth required pam_ldap.so.1 ># > > >Doesn''t work for me. I don''t have pam_unix_cred, since we never used kerberos here. Anyway all the docs say not to use it with LDAP. I tried what you had, without the pam_unix_cred, and no joy.. Sam
Susan wrote:>I have this and my dtlogin works fine: > > ># Default definitions for Authentication management ># Used when service name is not explicitly mentioned for authentication ># >other auth requisite pam_authtok_get.so.1 >other auth required pam_dhkeys.so.1 >other auth required pam_unix_cred.so.1 >other auth sufficient pam_unix_auth.so.1 >other auth required pam_ldap.so.1 ># > > >Susan, I''m pretty sure now that authentication is not the problem - it seems to authenticate fine and then die. What other lines for "other" do you have in your pam.conf? Sam
-bash-3.00# uname -a SunOS unknown 5.10 Generic_118822-27 sun4u sparc SUNW,Ultra-5_10 -bash-3.00# grep other /etc/pam.conf other auth requisite pam_authtok_get.so.1 debug other auth required pam_dhkeys.so.1 debug other auth required pam_unix_cred.so.1 debug other auth sufficient pam_unix_auth.so.1 debug other auth required pam_ldap.so.1 debug other account requisite pam_roles.so.1 other account required pam_unix_account.so.1 other session required pam_unix_session.so.1 other password required pam_dhkeys.so.1 debug other password requisite pam_authtok_get.so.1 debug other password requisite pam_authtok_check.so.1 debug other password required pam_authtok_store.so.1 server_policy debug -bash-3.00# if it goes through and THEN dies then something is wrong with your X setup. Did you look in messages for any X problems? dead font servers, read/write permissions for .Xauth files, etc...? --- Sam Smith <sam.smith@ece.gatech.edu> wrote:> Susan wrote: > > >I have this and my dtlogin works fine: > > > > > ># Default definitions for Authentication management > ># Used when service name is not explicitly mentioned for authentication > ># > >other auth requisite pam_authtok_get.so.1 > >other auth required pam_dhkeys.so.1 > >other auth required pam_unix_cred.so.1 > >other auth sufficient pam_unix_auth.so.1 > >other auth required pam_ldap.so.1 > ># > > > > > > > Susan, I''m pretty sure now that authentication is not the problem - it > seems to authenticate fine and then die. What other lines for "other" do > you have in your pam.conf? > > Sam > > -- > Fedora-directory-users mailing list > Fedora-directory-users@redhat.com > https://www.redhat.com/mailman/listinfo/fedora-directory-users >__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com