[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]


I'd be interested in looking at that patch for PAM. I started on it, but
got sidetracked.

I'm not sure what the right thing for msyslogd. I had thought /dev/log was
standard on Unix systems, but I see that FreeBSD puts in /var/run, too. The
odd thing is that I have it at /dev/log on FreeBSD Debian, and seems to
work... Maybe I better test it more.

AFAIK, only syslogd, and the syslog function in libc need to use that socket,
so it shouldn't really matter where it is, as long as both can find it.

On Sun, Feb 24, 2002 at 04:16:25AM +0000, Matthew Garrett wrote:
> I have PAM 0.75 source that builds and appears to work if I use shadow
> with it. 6 patches from the NetBSD port seem to be enough to get it to
> compile, but I needed to add a check for pwent->pwexpire being 0 (the code
> assumes that if the current time is greater than the expiry time then the
> password has expired, even if there isn't an expiry time set). With that
> done, I can rebuild my patched shadow utils with PAM and login seems to
> work.
> On a separate note, msyslogd builds happily but uses /dev/log as its
> socket by default. The NetBSD logging functions seem to be expecting
> /var/run/log - symlinking the two work, and you can pass an option to
> msyslog to make it produce /var/run/log instead. What's the preferable way
> to do this?
> -- 
> Matthew Garrett | mjg59@srcf.ucam.org
> -- 
> To UNSUBSCRIBE, email to debian-bsd-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Reply to: