Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the '10.3: Enable remote logging features' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.3: Enable remote logging features
Authored by: stetner on Nov 27, '03 06:14:23PM

I emailed this to another list
--------------------------
Yet another quick note on syslogd.

case 'u': /* only log specified priority */
UniquePriority++;
break;
and

static int UniquePriority = 0; /* Only log specified priority? */

(got to love that question mark at the end...)


So the 'u' is not insecure mode either any more. So now I use:

/usr/sbin/syslogd -m 15

For the record:

static void
usage(void)
{

fprintf(stderr, "%s\n%s\n%s\n%s\n",
"usage: syslogd [-46Acdknosuv] [-a allowed_peer]",
" [-b bind address] [-f config_file]",
" [-l log_socket] [-m mark_interval]",
" [-P pid_file] [-p log_socket]");
exit(1);
}
--------------------------
So, the '-s' flag turns on secure, if it is not there it is in insecure mode and the -u does some weird unique priority that I have not taken the time to figure out.

The current man page does NOT match what the source code is doing. I have filed a radar (bug) on this.



[ Reply to This | # ]