PAM problem

O. Hartmann ohartman at zedat.fu-berlin.de
Thu Feb 22 14:42:39 UTC 2007


Marinos Ilias wrote:
> Hello people,
> I 've just upgraded a system from 6.2 to 7.0 , and sudo doesn't work anymore , giving the following error:
> sudo: unable to initialize PAM: No such file or directory
> Of course the sudoers entries are ok and the user has the rights to invoke sudo.Sudo was working before upgrade.
> 
> I do not know if that problem has to do with some others that occurred to the system .All ports broke(give SEGV) after the upgrade and I had to deinstall & reinstall them.Sudo was installed from ports too.Should I try to reinstall it?If yes, what can cause that error?
> 
> 
> Thank you.
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"

I've also upgraded a box from 6.2 -> 7.0. But I had to recompile 
every(!) port to make them working properly. Have you recompiled sudo 
port? Or just taken it as it was (compiled from 6.2-sources)? If not 
recompiled the port, please recompile/reinstall.

Except Xorg (server is broken due to lack in a compiler option 7.0 
expects to see) everything seems to work well, even sudo in 7.0-CURRENT.

Regards,
Oliver




More information about the freebsd-current mailing list