From root@archive.jmrodgers.com Fri Mar  5 06:01:51 1999
Return-Path: <root@archive.jmrodgers.com>
Received: from archive.jmrodgers.com (archive.jmrodgers.com [205.247.224.207])
	by hub.freebsd.org (Postfix) with ESMTP id 53DF715174
	for <FreeBSD-gnats-submit@freebsd.org>; Fri,  5 Mar 1999 06:01:42 -0800 (PST)
	(envelope-from root@archive.jmrodgers.com)
Received: (from root@localhost)
	by archive.jmrodgers.com (8.8.8/8.8.8) id RAA13669;
	Thu, 4 Mar 1999 17:07:09 -0500 (EST)
	(envelope-from root)
Message-Id: <199903042207.RAA13669@archive.jmrodgers.com>
Date: Thu, 4 Mar 1999 17:07:09 -0500 (EST)
From: Max.Euston@archive.jmrodgers.com
Sender: root@archive.jmrodgers.com
Reply-To: max@core.net
To: FreeBSD-gnats-submit@freebsd.org
Subject: Bad cpu limit (60s) w/ getty+ppp
X-Send-Pr-Version: 3.2

>Number:         10399
>Category:       bin
>Synopsis:       Bad cpu limit w/ (60s) w/ getty+ppp
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    brian
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Mar  5 06:10:01 PST 1999
>Closed-Date:    Tue Mar 9 14:04:56 PST 1999
>Last-Modified:  Tue Mar  9 14:05:14 PST 1999
>Originator:     Max Euston
>Release:        FreeBSD 2.2.8-RELEASE i386
>Organization:
>Environment:

	2.2.8-RELEASE (but same problem with all versions)

>Description:

getty sets a SOFT cpu limit to 60 seconds to help detect hung lines.
It resets this to infinity before exec()ing login, but does not reset
it before exec()ing "ppplogin" (set with pp=... in /etc/gettytab).

>How-To-Repeat:

Set "pp=..." in /etc/gettytab and ppp-connect to this line.  The
connection will silently drop some time in the future (15 minutes to
several hours depending on line usage).

>Fix:

1) Apply this patch:

--- /src/libexec/getty/main.c.orig      Mon Dec 15 02:10:53 1997
+++ /src/libexec/getty/main.c   Wed Mar  3 14:58:44 1999
@@ -349,6 +349,9 @@
                if ((rval = getname()) == 2) {
                        oflush();
                        alarm(0);
+                       limit.rlim_max = RLIM_INFINITY;
+                       limit.rlim_cur = RLIM_INFINITY;
+                       (void)setrlimit(RLIMIT_CPU, &limit);
                        execle(PP, "ppplogin", ttyn, (char *) 0, env);
                        syslog(LOG_ERR, "%s: %m", PP);
                        exit(1);


2) Workaround:

Have "pp=..." set to a shell script that does a "ulimit -t unlimited"
(or limit for csh) before running "ppp -direct".



>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->brian 
Responsible-Changed-By: brian 
Responsible-Changed-When: Tue Mar 9 11:47:39 PST 1999 
Responsible-Changed-Why:  
ppp's mine 
State-Changed-From-To: open->closed 
State-Changed-By: brian 
State-Changed-When: Tue Mar 9 14:04:56 PST 1999 
State-Changed-Why:  
Fixed in -current. 
>Unformatted:
