>...and right now, they can't; it installs, but it fails to run on a
>stock 1.5 system.
>
>The thing is, I'm not sure what to do about it. However, since nobody
>else has made any suggestions, here's what I propose:

        I believe this is because of a bug in lib/libutil/login_cap.c,
        which i believe corrected already in 1.5 release.

>1. On the 1.5 (and possibly -current) branch, make login_getclass(3)
> synthesize a "default" entry if /etc/login.conf doesn't exist or
> is empty. Possibly (on the -current branch) also syslog a warning
> in this case. Alter the man page to document this behavior.

        i believe this is what we do already (synthesize entry if no login.conf
        exist). are you sure you have 1.5 libutil.a? don't you have
        1.5_ALPHA2 libutil?

        I don't have /etc/login.conf, and I can run sshd from pkgsrc
        just fine on both current and 1.5.1_ALPHA system. i don't have
        pure 1.5 system here, but from cvs revision number 1.5.1_ALPHA
        libutil should identical to 1.5 libutil.
        (and yes, all sshd references login_getclass)

itojun

lib/libutil/login_cap.c
---------------------------- current
revision 1.9
date: 2000/10/12 00:28:33; author: itojun; state: Exp; lines: +17 -7
/etc/login.conf is optional, so don't return NULL even if
there's none found. addresses part of PR 11150. sync with openbsd.
---------------------------- 1.5 branch (prior to 1.5 release)
revision 1.5.4.1
date: 2000/10/18 03:44:59; author: tv; state: Exp; lines: +70 -101
Pullup 1.6-1.9 [itojun]:
/etc/login.conf is optional, so don't return NULL even if
there's none found. addresses part of PR 11150. sync with openbsd.

[releng: plus some cosmetic changes making 1.6-1.8 necessary]

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]