#2843 closed task (invalid)
Fcron uses Pam by default
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | BOOK | Version: | SVN |
| Severity: | normal | Keywords: | |
| Cc: |
Description ¶
Fcron builds itself to use Pam, even when Pam is not installed.
root@ThirdFloor:~# fcrontab -l 02:18:56 Could not open PAM session: Permission denied
Adding:
--with-pam=no
fixes it.
Change History (5)
comment:1 by , 16 years ago
| Milestone: | 6.4 → 6.5 |
|---|
comment:2 by , 15 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
Can't confirm. I don't build PAM and I never had this issue at least with the current version 3.0.4 (which its a little bit dated anyway).
Closing as worksforme as there wasn't another confirmation from another user until now, neither a quick research in fcron's mailing list (neither google), neither a quick glance in fcron's sources showed up any evidence of the bug. If you are totally sure, please report it upstream and reopen if you think that there is a reason.
comment:3 by , 15 years ago
| Resolution: | worksforme |
|---|---|
| Status: | closed → reopened |
comment:4 by , 15 years ago
| Resolution: | → invalid |
|---|---|
| Status: | reopened → closed |
I can also confirm that without PAM installed, Fcron will proceed just fine without it. It recognizes that PAM is not installed and does not try to include the PAM libraries.
I'm not sure why Robert ran into this. Perhaps he had some old PAM headers and libraries around, but PAM was not configured to be used.
Anyway, closing the ticket as invalid.
Modified milestone from 6.4 to 6.5