Re: socklog-unix problem, on netbsd
Charlie Brady <[email protected]>
| Newsgroups | gmane.comp.misc.pape.general |
|---|---|
| Message-ID | <[email protected]> |
On Sat, 21 Jan 2006, George Georgalis wrote: >> # ktruss logger hello ... >> 5343 logger socket(0x1, 0x2, 0) = 1 >> 5343 logger fcntl(0x1, 0x2, 0x1) = 0 >> 5343 logger connect(0x1, 0xbdbe9420, 0xe) Err#2 ENOENT >> 5343 logger close(0x1) = 0 >> 5343 logger sendto(0xffffffff, 0xbfbfdcc0, 0x1f, 0, 0, 0) Err#9 EBADF >> 5343 logger close(0xffffffff) Err#9 EBADF >> 5343 logger socket(0x1, 0x2, 0) = 1 >> 5343 logger fcntl(0x1, 0x2, 0x1) = 0 >> 5343 logger connect(0x1, 0xbdbe9420, 0xe) Err#2 ENOENT >> 5343 logger close(0x1) = 0 >> 5343 logger sendto(0xffffffff, 0xbfbfdcc0, 0x1f, 0, 0, 0) Err#9 EBADF >> 5343 logger close(0xffffffff) Err#9 EBADF >> 5343 logger exit(0) Exit 0 eh? And sendo(-1, ...)? Looks like "logger" is very careless about checking return values of system calls.