bin/81555: Cron exits from SIGPIPE after crontab -e when using NSS-LDAP

[Dean Strik]

>Number:         81555
>Category:       bin
>Synopsis:       Cron exits from SIGPIPE after crontab -e when using NSS-LDAP
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri May 27 13:00:13 GMT 2005
>Closed-Date:
>Last-Modified:
>Originator:     Dean Strik
>Release:        FreeBSD 5.4-RELEASE-p1
>Organization:
Eindhoven University of Technology
>Environment:
FreeBSD tesla.stack.nl 5.4-RELEASE-p1 FreeBSD 5.4-RELEASE-p1 #2: Tue May 17 19:53:43 CEST 2005     root at snail.stack.nl:/usr/obj/usr/src/sys/SMP  i386

SMP system (dual P2-233) using NSS-LDAP (static root).
>Description:

	Cron(8) seems to exit after a SIGPIPE when a user runs crontab
-e.  This way normal users can effectively, even without intent, easily
kill the cron daemon, so this is serious.

	I ktraced one cron daemon, and it shows a SIGPIPE (and therefore
exit) after using NSS-LDAP lookups. So local users do not trigger the
problem, but LDAP users do.

>How-To-Repeat:
	As local user with account info in LDAP, run crontab -e and save.
>Fix:
	Haven't looked at a fix yet, but perhaps ignoring SIGPIPE is the
way to here.
>Release-Note:
>Audit-Trail:
>Unformatted: