[wt4hq] Broken Pipe

[Olivier F5MZN]

Halo,

>> About EINTR signal: this should be handled by the "default" case 
>> statement, which will issue in a disconnect. Do you suggest to handle it 
>> differently?
> 
> Yes, I do. Albeit it is unlikely in your code that a signal would ever occur,
> the common Unix idiom is to handle EINTR like EAGAIN, since EINTR is not
> a failure indication, its just that the operation was interrupted by some
> signal occuring and couldn't be completed this time.
> Therefore, imho, trying again is much more sensible,
> otherwise you kill your client connection for no reason, and run 
> the risk of losing a QSO (or, worse, a GAB)...

Actually, I still have some gaps regarding signal handling on socket 
programming so any recommandations are welcome, Mario!

Can you send me a suggested modification? I should rather create a CVS 
or SVN access to let you modify by yourself but I'm always too busy to 
find a couple a minutes for that!

> (When reading through my mails again and again, you might notice I'm
> sounding like an advanced case of paranoia, but hey, thats OK :)

NP, it's OK with me! I'm also concerned with security aspects because 
it's 80% of my job!

> On a related note, Olivier, will you be in Friedrichshafen at Ham Radio
> next weekend?

Yes, the WT team will be at FHN this year. We will be hosted at the 
Apello booth, feel free to visit us! We will also take part to the great 
BCC diner on Saturday.

73,
-- 
Olivier / f5mzn