Cameron> Would it make sense to put in a small diagnostic so that
Cameron> an attempt to
Cameron> 1. bind a trap-handler to a session configured
Cameron> to other-than-162, or
Cameron> 2. reconfigure a session already bound to a
Cameron> trap-handler to an other-than-162 port
Cameron> returns an explanation of the fact that Tnm does *not*
Cameron> support such trap reception?
I understand why you suggest this, but I prefer to fix it instead of
spending time to add warning messages for things like this. Note that
this problem has already been fixed in the UNIX straps forwarder. All
I need to do is to rework the session configuration options, which
will include some minor incompatibilities. The tricky part is that
every change to a trap port option requires to re-bind to a new straps
daemon. I hope that this will part of 2.2.0.
Juergen
-- Juergen Schoenwaelder schoenw@cs.utwente.nl http://www.cs.utwente.nl/~schoenw Computer Science Department, University of Twente, (Fax: +31-53-489-3247) P.O. Box 217, NL-7500 AE Enschede, The Netherlands. (Tel. +31-53-489-3678)