From owner-freebsd-commit  Wed Jan 31 07:16:19 1996
Return-Path: owner-commit
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id HAA07988
          for freebsd-commit-outgoing; Wed, 31 Jan 1996 07:16:19 -0800 (PST)
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id HAA07925
          for cvs-all-outgoing; Wed, 31 Jan 1996 07:16:06 -0800 (PST)
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id HAA07858
          for cvs-usrsbin-outgoing; Wed, 31 Jan 1996 07:16:01 -0800 (PST)
Received: (from wpaul@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id HAA07830
          Wed, 31 Jan 1996 07:15:56 -0800 (PST)
Date: Wed, 31 Jan 1996 07:15:56 -0800 (PST)
From: Bill Paul <wpaul>
Message-Id: <199601311515.HAA07830@freefall.freebsd.org>
To: CVS-committers, cvs-usrsbin
Subject: cvs commit: src/usr.sbin/yppush yppush_main.c
Sender: owner-commit@FreeBSD.ORG
Precedence: bulk

wpaul       96/01/31 07:15:52

  Modified:    usr.sbin/yppush  yppush_main.c
  Log:
  Sync with my sources at home:
  
  - Don't do longjmp()s from inside a signal handler. Even though I got
    things to work the way I wanted, it's bad karma.
  
  - Remember to clear the sa_mask with sigemptyset() before masking signals
    when using sigaction() to set up the SIGIO handler.
  
  - Break out of the wait loop in yppush_exit() when the five minute
    timeout expires instead of looping around for another pass. If ypxfr
    on the other end fails somehow and never sends a response, we don't
    want to wait around forever.
  
  Revision  Changes    Path
  1.2       +39 -4     src/usr.sbin/yppush/yppush_main.c