diff options
author | guy <guy@f5534014-38df-0310-8fa8-9805f1628bb7> | 2004-01-24 10:53:25 +0000 |
---|---|---|
committer | guy <guy@f5534014-38df-0310-8fa8-9805f1628bb7> | 2004-01-24 10:53:25 +0000 |
commit | 484071c232b2f8512db920efa9148473c59f726d (patch) | |
tree | 4f33de0c36a5dc83443857df1e1cd4ff680fbe32 /packet-rmcp.c | |
parent | c484a2b17f88a61c345a776443722d07e094b06c (diff) |
As with "file_write_error_message()", so with
"file_close_error_message()" - but just use "file_write_error_message()"
for UNIX-style errors, under the assumption that a close will only fail
because a buffer-flushing write fails or because "close()" itself fails
when, for example, pushing unsynced NFS client-side writes out over the
wire.
Make several routines in "print.c" return success/failure indications.
Check for write errors when printing "Follow TCP Stream" stuff or saving
it to a file.
git-svn-id: http://anonsvn.wireshark.org/wireshark/trunk@9825 f5534014-38df-0310-8fa8-9805f1628bb7
Diffstat (limited to 'packet-rmcp.c')
0 files changed, 0 insertions, 0 deletions