bin/81555: Cron exits from SIGPIPE after crontab -e when using
NSS-LDAP
Dick Davies
rasputnik at hellooperator.net
Wed Jun 22 20:40:20 GMT 2005
The following reply was made to PR bin/81555; it has been noted by GNATS.
From: Dick Davies <rasputnik at hellooperator.net>
To: Dean Strik <dean at stack.nl>
Cc: bug-followup at FreeBSD.org
Subject: Re: bin/81555: Cron exits from SIGPIPE after crontab -e when using NSS-LDAP
Date: Wed, 22 Jun 2005 21:33:07 +0100
* Dean Strik <dean at stack.nl> [0625 16:25]:
> Dick Davies wrote:
> > This also appears to be an issue with non-ldap users on 5.4, providing the system
> > has some nss_ldap accounts. I'm not sure whether it's because my initial (ssh) login
> > was nss_ldap based.
>
> Actually it must've been because of your ssh login was nss-ldap based.
> You can verify this by restarting sshd after putting your account in
> /etc/passwd to test.
>
> By the way, simply ignoring the SIGPIPE works well for me. Trivial patch
> attached.
>
> Cheers,
> Dean
>
> --
> Dean C. Strik Eindhoven University of Technology
> dean at stack.nl | dean at ipnet6.org | http://www.ipnet6.org/
> "This isn't right. This isn't even wrong." -- Wolfgang Pauli
> --- usr.sbin/cron/cron/cron.c Sun Jun 12 17:18:18 2005
> +++ usr.sbin/cron/cron/cron.c Sun Jun 12 17:18:36 2005
> @@ -80,6 +80,7 @@
>
> parse_args(argc, argv);
>
> + (void) signal(SIGPIPE, SIG_IGN);
> #ifdef USE_SIGCHLD
> (void) signal(SIGCHLD, sigchld_handler);
> #else
That helped for me, thanks - is there any obvious downside to this ?
--
'Why pay the earth for expensive jigsaws? Just take a bag of frozen chips
from the freezer and try piecing together potatoes.'
-- B Reastford, Iranville, Notts.
Rasputin :: Jack of All Trades - Master of Nuns
More information about the freebsd-bugs
mailing list