В Tue, 13 Jan 2015 17:41:13 +0100 "Carlos E. R." <robin.listas@telefonica.net> пишет:
On 2015-01-13 17:21, Andrei Borzenkov wrote:
В Tue, 13 Jan 2015 16:34:47 +0100 "Carlos E. R." <> пишет:
...
The manual explains -Lf, but not -LF.
I would not call the part you yourself quoted "does not explain". What is missing then?
A separate paragraph for -LF and -Lf, for instance. The wording is not clear: perhaps you understand it, but I don't.
From my tests, Lf seems to be a pipe, LF a file.
Both are file as explained above in manual.
No, with -Lf I get a pipe or something, not a file - see the "=" at the end:
Because syntax is wrong. As written in manual, difference between Lf and LF (or small and capital form in general) is extra argument that sets priority. So in -Lf n /var/log/net-snmpd.log "-Lf n" is log file option (may be you have file with name "n" somewhere now) and /var/log/net-snmpd.log is interpreted as normal argument which is "listening address". So snmptrapd simply attempts to listen on it; because it looks like file name, it is interpreted as Unix domain socket. "-Lf /path/to/file" vs. "-LF <prio> /path/to/file" I said it was not for the faint of heart, did I? :)
AmonLanc:~ # l /var/log/net-snmpd.log srwxr-xr-x 1 root root 0 Jan 13 15:57 /var/log/net-snmpd.log= AmonLanc:~ #
The result is that I can not even try to read it:
AmonLanc:~ # less /var/log/net-snmpd.log /var/log/net-snmpd.log is not a regular file (use -f to see it) AmonLanc:~ # less -f /var/log/net-snmpd.log /var/log/net-snmpd.log: No such device or address AmonLanc:~ #