From: firstname.lastname@example.org.DE (Rolf-Thomas Happe)
Date: 12 Sep 1996 18:27:19 -0400
The function autoreap-policy apparently hasn't read the manual
(draft Nov 1, 1995 - 15:58, section 3.4.1). Respectively, the
manual should point out, that the policy id has to be wrapped
in a list: (autoreap-policy #f) does not change the policy,
(autoreap-policy '(#f)) does, (autoreap-policy '()) works,
(autoreap-policy) causes an error (wrong number of arguments).
The definition in procobjs.scm actually says
(define (autoreap-policy maybe-policy) ...
Yes -- I left out a dot. This:
(define (autoreap-policy maybe-policy)
should be this:
(define (autoreap-policy . maybe-policy)
So AUTOREAP-POLICY's optional arg wasn't. I have fixed the sources;
it'll be in the next release, due out sometime before the turn of the
Thank you for the bug report.
The policy 'late documented in section 3.4.1 isn't supported.
You aren't going to get 'late until we switch to a release of s48
that has gc finalisation.
BTW, the zombie generated by
(read (run/port (cat) (< schmonzes.scm)))
survives an explicit ,collect (with 'early autoreaping). While the
above line is not meant to make much sense, it would be nice if one
could perform similar operations without having to bother about
process reaping, just as one can (run (ps)) and don't care for
This is as-documented in the manual -- in the current release, early reaping
happens at the next wait call (which could be your next (RUN ...) form).
The version of scsh on which I am working has signal handlers,
so I can now do *very* aggressive autoreaping by using the SIGCHLD
signal to trigger reaping, so as soon as the process dies, scsh will
scarf it up.
We'll get the new system out to you as soon as we can.