Project

General

Profile

Bug #3232

syslogd shouldn't sync after each LOG_KERN line

Added by Arne Jansen about 8 years ago. Updated about 7 years ago.

Status:
Feedback
Priority:
Normal
Assignee:
Category:
-
Start date:
2012-09-27
Due date:
% Done:

80%

Estimated time:
Difficulty:
Medium
Tags:
needs-triage
Gerrit CR:

Description

currently syslogd fdsyncs after each LOG_KERN line. This slows down the output significantly. Instead if should not sync when more messages are pending.

#1

Updated by Rich Lowe about 8 years ago

  • Project changed from OpenIndiana Distribution to illumos gate
#2

Updated by Gary Mills about 7 years ago

  • Status changed from New to In Progress
  • Assignee set to Gary Mills
  • % Done changed from 0 to 80

My strategy is to detect bursts of kernel messages by calling poll() repeatedly with zero timeout until there are no more messages. Then the sys_poll thread issues a sync and sleeps in a poll() with infinite timeout.

#3

Updated by Gary Mills about 7 years ago

  • Status changed from In Progress to Feedback

I've abandoned this bug fix pending further information. Omitting the sync after every write of a system message to a log file may result in lost messages. Has anybody encountered a performance problem as a result of the frequent syncs? If not, it's better to leave the syslogd code unchanged.

Also available in: Atom PDF