Fix a comment; this includes describing an additional way in which we
could fail to open the capture file. svn path=/trunk/; revision=38695
This commit is contained in:
parent
2ab112d5dd
commit
898334c7a5
|
@ -1612,11 +1612,19 @@ sync_pipe_input_cb(gint source, gpointer user_data)
|
|||
alerted. Close the sync pipe. */
|
||||
ws_close(source);
|
||||
|
||||
/* the child has send us a filename which we couldn't open.
|
||||
this probably means, the child is creating files faster than we can handle it.
|
||||
this should only be the case for very fast file switches
|
||||
we can't do much more than telling the child to stop
|
||||
(this is the "emergency brake" if user e.g. wants to switch files every second) */
|
||||
/* The child has sent us a filename which we couldn't open.
|
||||
|
||||
This could mean that the child is creating files faster
|
||||
than we can handle it. (XXX - why would that result in
|
||||
a failure to open the file?)
|
||||
|
||||
That should only be the case for very fast file switches;
|
||||
We can't do much more than telling the child to stop.
|
||||
(This is the "emergency brake" if the user e.g. wants to
|
||||
switch files every second). */
|
||||
|
||||
This can also happen if the user specified "-", meaning
|
||||
"standard output", as the capture file. */
|
||||
sync_pipe_stop(capture_opts);
|
||||
capture_input_closed(capture_opts, NULL);
|
||||
return FALSE;
|
||||
|
|
Loading…
Reference in New Issue