| Summary: | distcc shouldn't send messages to syslog | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | nile <automaticbox> |
| Component: | Current packages | Assignee: | Lisa Seelye (RETIRED) <lisa> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Uh, can't you just set your syslogger to ignore distcc if you don't want it? This is not a bug. Edit your logger config file or use --log-file. |
Distcc shouldn't fill syslog with a bunch of random messages. Output should be directed to a log file (/var/log/distcc.log works well). Reproducible: Always Steps to Reproduce: 1. Start distccd server 2. Get jobs 3. Watch logs fill up Actual Results: /var/log/messages gets huge, people tailing /var/log/messages get annoyed, lots of other stuff =P Expected Results: Distcc should direct log messages to a log file. This is from the man page for distccd: --log-file FILE Send messages to file FILE instead of syslog. Logging directly to a file is significantly faster than going via syslog and is recommended. Okay! My really ugly and dirty hack to fix this was adding the "--log-file" line to /etc/init.d/distccd: /sbin/start-stop-daemon --start --quiet --startas ${DISTCCD_EXEC} \ --pidfile ${DISTCCD_PIDFILE} -- \ --pid-file ${DISTCCD_PIDFILE} -N ${DISTCCD_NICE} --user distcc \ --log-file /var/log/distccd.log A prettier fix would be to set a log file option in /etc/conf.d/distccd.