-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Daniel Kahn Gillmor wrote: > On 03/15/2010 01:15 AM, Chris Taylor wrote: >> That does indeed appear to be the origin of the limit. Although sanely >> dying, or notifying, when trying to open a socket with a longer file >> name than 108 chars should be appropriate. > > There appears to be a Warn2 logging message in the code already, so it > shows up when you supply a -d argument to socat. > > Maybe this should be switched to an error message so that it shows by > default? > > Or maybe it should be a fatal error? It seems potentially dangerous to > just push ahead with a truncated name, though. what if the truncated > name already exists and is in use for something else? > > --dkg >
I would actually lean more towards making it a fatal error instead. I agree that just truncating and continuing could be dangerous. - -Chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkuecAYACgkQLpNUoan9SCEcYwCeJqTNielXxAMWOKh33+Kr7lrD lZgAn0k7/Sg+J06llC2nRypZLfWsQOin =lMUP -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
