Project

General

Profile

Actions
Copy link

Bug #6838

closed
JP JP

bsnmpd logs errors when /etc/printcap is missing

Bug #6838: bsnmpd logs errors when /etc/printcap is missing

Added by Jim Pingle almost 10 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Jim Pingle
Category:
SNMP
Target version:
2.3.3
Start date:
10/05/2016
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.3.x
Affected Architecture:

Description

We do not ship with an /etc/printcap file but it appears that bsnmpd does not like that fact. When probed in various ways (especially when querying SNMP OID 1.3.6.1.2.1.25.3.5 ), bsnmpd logs an error to the system log:

snmpd[67512]: hrPrinterTable: printcap entry for <noname?> has errors, skipping

With an empty /etc/printcap (touch /etc/printcap), no errors are logged.

We could include a blank printcap or include the FreeBSD default printcap file which is logically empty as it all of its contents are comments.

KB Updated by Kill Bill almost 10 years ago Actions
Copy link
 #1

Yeah, filed this as #6810, please close that one as duplicate.

JP Updated by Jim Pingle almost 10 years ago Actions
Copy link
 #2

Somehow I completely missed that ticket when looking into this. I'll close the older one out since this one has a viable workaround on it.

JP Updated by Jim Pingle almost 10 years ago Actions
Copy link
 #3

  • Assignee set to Jim Pingle

JP Updated by Jim Pingle almost 10 years ago Actions
Copy link
 #4

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

Applied in changeset commit:63b44eed9eeaa32567c1234c37dbce2e15dc8d37.

JP Updated by Jim Pingle over 9 years ago Actions
Copy link
 #5

  • Status changed from Feedback to Resolved

Seems to be fine now, no more log spam and the dummy printcap file is there as expected.

JP Updated by Jim Pingle over 9 years ago Actions
Copy link
 #6

  • Target version changed from 2.4.0 to 2.3.3
Actions
Copy link

Also available in: Atom