From: Sergey Lebedev <barabashka@vgg.ru> To: community@lists.altlinux.org Subject: [Comm] Проблема с crond и pam_access Date: Tue, 7 Mar 2006 12:22:06 +0300 Message-ID: <20060307092206.GA12058@vgg.ru> (raw) Система Master2.4 + updates. После добавления в /etc/pam.d/system-auth строчки account required pam_access.so В логи стали падать следующие сообщения crond[22235]: (CRON) pam_acct_mgmt failed (Critical error - immediate abort) И соответственно не отрабатывает cron. /etc/security/access.conf пуст. Удаляю pam_access из system-auth, cron начинает работать. Отказаться от pam_access нет возможности ибо студенты не спят и на сервер попасть всегда желают. :) Так что хотелось бы узнать в чем причина и как это лечиться (cron + pam_access, а не студенты) :) pam-config-1.1.7-alt1 pam-0.75-alt27 pam0_tcb-0.9.8.8-alt1 pam0-config-1.1.7-alt1 pam0_console-0.75-alt27 pam_krb5-2.0.10-alt1 pam_ldap-169-alt1 libpam0-0.75-alt27 pam0_passwdqc-0.7.5-alt2 pam0_userpass-0.9.1-alt2 crontab-control-1.0-alt1 crontabs-1.8-alt1 vixie-cron-4.0.b1.20040604-alt2 anacron-2.3-ipl9mdk Содержимое /etc/pam.d/system-auth #%PAM-1.0 auth sufficient pam_ldap.so auth required pam_tcb.so shadow fork prefix=$2a$ count=8 nullok use_first_pass account required pam_access.so account sufficient pam_ldap.so account required pam_tcb.so shadow fork password required pam_passwdqc.so min=disabled,24,12,8,7 max=40 passphrase=3 match=4 similar=deny random=42 enforce=users retry=3 password sufficient pam_ldap.so use_authtok password required pam_tcb.so use_authtok shadow fork prefix=$2a$ count=8 write_to=tcb session required pam_tcb.so session required pam_limits.so session required pam_mkhomedir.so skel=/etc/skel.ru_RU.KOI8-R/ umask=0026
reply other threads:[~2006-03-07 9:22 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20060307092206.GA12058@vgg.ru \ --to=barabashka@vgg.ru \ --cc=community@lists.altlinux.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
ALT Linux Community general discussions This inbox may be cloned and mirrored by anyone: git clone --mirror http://lore.altlinux.org/community/0 community/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 community community/ http://lore.altlinux.org/community \ mandrake-russian@linuxteam.iplabs.ru community@lists.altlinux.org community@lists.altlinux.ru community@lists.altlinux.com public-inbox-index community Example config snippet for mirrors. Newsgroup available over NNTP: nntp://lore.altlinux.org/org.altlinux.lists.community AGPL code for this site: git clone https://public-inbox.org/public-inbox.git