Bug 6871 – PPPD gets sighup using RP3 to dial, fine in KPPP

Bug 6871 - PPPD gets sighup using RP3 to dial, fine in KPPP

Summary:	PPPD gets sighup using RP3 to dial, fine in KPPP

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	rp3 (Show other bugs)
Sub Component:
Version:	6.1
Hardware:	i386 Linux

Priority	medium Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Michael K. Johnson
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-11-10 01:05 EST by bkosse
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	1999-11-10 10:16:25 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description bkosse 1999-11-10 01:05:57 EST

Very often, the first time I try to connect to my ISP (using
RP3), PPP will make a connection and log on but immediately
get a SIGHUP after the Connect: ppp0 <--> /dev/ttyS2 line.

This doesn't happen with KPPP or with a manually created
ppp-on script. It did, however, also happen with the
original RH 5.x netcfg script, presumably with the netcfg
script in 6.1 as well.

Comment 1 Bill Nottingham 1999-11-10 10:16:59 EST

This is fixed in the errata pppd release.

Note You need to log in before you can comment on or make changes to this bug.