On Fri, 15 Aug 2008 10:05:19 -0700 (PDT) bugzilla-daemon at np.grommit.com wrote:
> In the next ksh93 update in Solaris, the ksh93 built-in sleep will be > replacing > Solaris /usr/bin/sleep. > Solaris /usr/bin/sleep will catch the SIGALRM but do nothing. The sleep > continues and effectively ignores the signal, eventually exiting with > status 0. > The AST ksh93 built-in sleep will do the default action for SIGALRM: > it terminates and exits with 142 (128 + 14 (the signal # for SIGALRM). > Although both behaviors are allowed by the standard, the differing > behavior will be an incompatibility when ksh93 sleep replaces > Solaris /usr/bin/sleep. isn't this simply the difference between a builtin command and an a.out? can you show 2 test cases, one with /usr/bin/sleep and one with the ksh93 builtin sleep I'm particularly interested in how SIGALRM is delivered i.e., the pid to kill in both cases -- Glenn Fowler -- AT&T Research, Florham Park NJ --
