Robert Goldman <rpgoldman@...> writes:
> I've had something like this happen to me before, but I'm afraid my
> memory is a bit hazy about it. IIRC, it happened to me on a program
> that was being run by a daemon, and there was some oddity about
> restoring *error-output* and/or *standard-output* with some piping we
> were doing. Is it possible that something is trying to read from the
> terminal without being properly hooked up to the terminal?
> Sorry I can't be more precise; I didn't take notes when we encountered
> and then fixed this bug. I mention this on the off-chance it will
> suggest something.
Well, as I say, this only seems to happen when the system boots
and launches `screen' from /etc/rc.local --- I haven't seen it
lock up when I run the thing interactively, so it kinda sounds right,
although it doesn't suggest anything to me. I'm not really expecting
to be able to track this down; it sounds like a SBCL bug to me.
I reported it on the off chance that it would spark some AHA reaction
in a maintainer. Especially the bit about GET-INTERNAL-REAL-TIME seems
But thanks for your input!