On Sat, 2018-01-06 at 23:52 +0900, Tetsuo Handa wrote: > Thank you. But excuse me? > Something unexpected must be happening in your environment. > > udplogger will flush buffers upon '\n' or timeout (default is 10 > seconds) or > too long line (default is 65536 bytes). Very strange because neither '\n' not 10 seconds helps to flush buffers. $ echo -e "test\n" > /dev/udp/127.0.0.1/6666 May be I used obsolete source? Could you check this? > > > > > Also i fixed two segfault: > > > > 1) When send two messages in one second from different hosts or > > ports. > > For reproduce just run > > "echo test > /dev/udp/127.0.0.1/6666 && echo test > > > /dev/udp/127.0.0.1/6666" > > in console. > > I can't observe such problem. > udplogger is ready to concurrently receive from multiple sources. Too strange because this condition https://github.com/kohsuke/udplogger/blob/master/udplogger.c#L82 do not allow open two file in one second. > > > > 2) When exced limit of open files. > > Just run "echo test > /dev/udp/127.0.0.1/6666" more than 1024 > > times. How much your "ulimit -n" ? My is 1024. $ ulimit -n 1024 May be your ulimit much greater or you launch udplogger under root? > > Are you using special environment? What is the shell? What is the > compiler/version? > $ gcc --version gcc (GCC) 7.2.1 20170915 (Red Hat 7.2.1-2) Copyright (C) 2017 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
