Niels,
>Perhaps you're right. But using names instead of numbers requires a
>change of the protocol, not just a clarification.
True. Which is why you might want to bring this up at <[EMAIL PROTECTED]>.
>Perhaps nobody uses signals. But I can imagine uses for signal
>forwarding. Say that you want run a remote program, that does certain
>things when signaled. Then you could request that your ssh-client
>forwards, say, SIGINT or SIGHUP; when you signal the client process,
>it delivers the signal to the remote process. This would naturally be
>most useful for deamon-like programs which don't offer any command
>line or other user interface. Even if I admit that remote deamons
>sounds a little bizarre.
Your example is just a little far fetched ;-)
There are much better ways to communicate across the network than using *nix
signalling. Actually, I'm somewhat suprised if it's still in there after
becoming an IETF draft. Eh, as a matter of fact, I did re-read it recently
but have to admit I didn't cared for that particular matter (which can be
explained by the fact that I'm at it from the Java environment perspective
;-).
Tomas
