Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.networking > #2906
| From | gof@somewhere.invalid (Adam Wysocki) |
|---|---|
| Newsgroups | comp.os.linux.networking |
| Subject | Re: how debug sockets |
| Date | 2014-04-14 13:15 +0000 |
| Organization | ATMAN - ATM S.A. |
| Message-ID | <gof.1397481282.6160@somewhere.invalid> (permalink) |
| References | <ef4e1391-8197-4f93-b97b-60c61398b1cf@googlegroups.com> |
xeon Mailinglist <xeonmailinglist@gmail.com> wrote: > how can I debug a socket to have more info about the reason why this is happening? > > Is there bash commands or socket logs where I can look? Try strace(1) or tcpdump(8). AW
Back to comp.os.linux.networking | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
how debug sockets xeon Mailinglist <xeonmailinglist@gmail.com> - 2014-04-13 06:00 -0700
Re: how debug sockets gof@somewhere.invalid (Adam Wysocki) - 2014-04-14 13:15 +0000
Re: how debug sockets Jorgen Grahn <grahn+nntp@snipabacken.se> - 2014-04-14 14:08 +0000
csiph-web