From owner-freebsd-isp Tue Mar 31 11:06:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA20154 for freebsd-isp-outgoing; Tue, 31 Mar 1998 11:06:00 -0800 (PST) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from ec.camitel.com (merlin.ec.camitel.com [206.231.123.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA20134 for ; Tue, 31 Mar 1998 11:05:57 -0800 (PST) (envelope-from cfortin@ec.camitel.com) Received: (from cfortin@localhost) by ec.camitel.com (8.8.8/8.8.7) id OAA01181 for freebsd-isp@FreeBSD.ORG; Tue, 31 Mar 1998 14:11:03 -0500 (EST) (envelope-from cfortin) Message-ID: X-Mailer: XFMail 1.2 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 31 Mar 1998 14:11:03 -0500 (EST) From: Pitou@ec.camitel.com To: freebsd-isp@FreeBSD.ORG Subject: Is /etc/login.conf is able to work with NIS ? Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is /etc/login.conf is able to work with NIS ? I run with FreeBSD on an NIS/NFS network. I want to be a xuser (Unlimited ressources!), but the tag ressource (xuser), is not avalable when I make an: ypcat passwd Somebody have an idea for upgrade my ressource limit, and continue to be on NIS ? (Because I think then the login program is not able to find the login.conf entry in the /etc , because the login program query the NIS by default. And the NIS not contain the login class information. The only solution then I can see is: I must create a new entry with my regular login info, including the class definition, in the /etc/passwd of my machine for bypass the NIS query. Any suggestion will be apreciate. Thank's To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message