From owner-freebsd-hackers Wed Jul 26 22:14:23 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id WAA06306 for hackers-outgoing; Wed, 26 Jul 1995 22:14:23 -0700 Received: from virgo.ai.net (virgo.ai.net [198.69.44.2]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id WAA06300 for ; Wed, 26 Jul 1995 22:14:20 -0700 Received: from aries.ai.net (aries.ai.net [198.69.44.1]) by virgo.ai.net (8.6.11/8.6.12) with ESMTP id BAA13034 for ; Thu, 27 Jul 1995 01:23:01 -0400 Received: (from nc@localhost) by aries.ai.net (8.6.11/8.6.12) id BAA25741; Thu, 27 Jul 1995 01:12:52 -0400 Date: Thu, 27 Jul 1995 01:12:52 -0400 (EDT) From: Network Coordinator To: hackers@freebsd.org Subject: Sliplogin exit 256?! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hackers-owner@freebsd.org Precedence: bulk I have been having problem with random slip line failures. A line will be working just fine, and then for no reason, and without a single modification [or reboot] to any file, slip login will begin to fail for that user. Not all users mind you, just one or two here or there. The error it gives is exit 256, which as far as I can tell is undocumented. The only way I can get these to work again is by essentially moving the account name around in the slip.hosts file [not reconfiguring, just moving it from say line 3, to line 13, and then when it fails later, I move it to line 5, etc.] Any ideas or similar experiences? Thanks, -Jerry.