From owner-freebsd-questions Thu Nov 9 17:16:19 2000 Delivered-To: freebsd-questions@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 8D5FF37B479 for ; Thu, 9 Nov 2000 17:16:06 -0800 (PST) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id LAA08826; Fri, 10 Nov 2000 11:45:11 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 10 Nov 2000 11:45:11 +1030 (CST) From: "Daniel O'Connor" To: petro Subject: RE: PPPD! Cc: FreeBSD-questions@FreeBSD.ORG Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 09-Nov-00 petro wrote: > I try to start pppd but always receive such message when start pppd > Device cuaa0 is busy... > What I must do, I try to kill all pppd and then start again, but again > receive such message, before rebbot everything works fine.... This belongs on -questions, so I've redirected it. Pppd uses UUCP locks to cooperate with other programs, but if some other process has locked the device (eg a terminal program like cu, or minicom, or another copy of pppd) it will say the device is busy. If you look in /var/spool/lock you may find some files who names begin with LCK, cat them and they should show a process ID, use 'ps -ax' to find out what process is holding the lock. Also, use ppp instead of pppd it is maintained regularly whereas pppd isn't (I think). --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message