Bug#486875: snmpd option syntax changed

2009-04-24 Thread Mathieu Parent
Feedback...

On Thu, Apr 23, 2009 at 10:55 PM, Mathieu Parent math.par...@gmail.com wrote:

 As a workaround, I will test tomorrow if the following syntax works :
 snmpd -LS 0-4d
^__ Doesn't work

 or snmpd -LS 4d
^__ Works

Mathieu Parent



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#486875: snmpd option syntax changed

2009-04-23 Thread Mathieu Parent
notforwarded 486875
thanks

Hi,

The good patch is here:
http://net-snmp.svn.sourceforge.net/viewvc/net-snmp/branches/V5-4-patches/net-snmp/snmplib/snmp_logging.c?r1=16721r2=17350pathrev=17350

changelog
CHANGES: snmpd, apps: Parser of -LS command line argument now accepts
both '-LS level facility' and '-LS levelfacility'.

Before patch #1806336 the first syntax was the only one supported. The patch
changed the syntax to the second one, causing incompatibilities in stable
branches. We now support both of them.


As a workaround, I will test tomorrow if the following syntax works :
snmpd -LS 0-4d

or snmpd -LS 4d
(see https://bugzilla.redhat.com/show_bug.cgi?id=477768#c7)

Mathieu Parent



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#486875: snmpd option syntax changed

2008-10-13 Thread Mathieu Parent
reopen 486875 =
thanks

Hi,

2008/10/11 Thomas Viehmann [EMAIL PROTECTED]:
 Hi Matthieu,

 as per the help output of snmpd and snmpcmd(1) (referenced by snmpd(8))
 the logging command line options snmpd have indeed changed.
 This might be inconvenient, but I fail to see how this is a bug in the
 common sense of the word.

I know that the logging command line have changed but the way I want
corresponds to the current (5.4.1~dfsg-9) snmpcmd man page:

=
LOGGING OPTIONS
   The  mechanism  and destination to use for logging of warning and error
   messages can be controlled by passing  various  parameters  to  the  -L
   flag.

   -LeLog messages to the standard error stream.

   -Lf FILE
  Log messages to the specified file.

   -LoLog messages to the standard output stream.

   -Ls FACILITY
  Log  messages  via syslog, using the specified facility ('d' for
  LOG_DAEMON, 'u' for LOG_USER, or '0'-'7' for LOG_LOCAL0  through
  LOG_LOCAL7).


   There  are  also  upper case versions of each of these options, which
   allow the corresponding logging mechanism to be restricted  to  certain
   priorities of message.  Using standard error logging as an example:

   -LE pri
  will log messages of priority 'pri' and above to standard error.

   -LE p1-p2
  will log messages with priority between 'p1'  and  'p2'  (inclu-
  sive) to standard error.

   For  -LF  and  -LS  the priority specification comes before the file or
   facility token.  The priorities recognised are:

  0 or !  for LOG_EMERG,
  1 or a for LOG_ALERT,
  2 or c for LOG_CRIT,
  3 or e for LOG_ERR,
  4 or w for LOG_WARNING,
  5 or n for LOG_NOTICE,
  6 or i for LOG_INFO, and
  7 or d for LOG_DEBUG.

   Normal output is (or will be!) logged at a priority level of LOG_NOTICE
=

As I understand, snmpd -LS 0-4 d is wellformed and mean: log via
syslog under facility LOG_DAEMON restricted to priorities LOG_EMERG to
LOG_WARNING.


 Kind regards

 T.

 P.S.: When reopening, please CC the bug so everyone sees your explanation.
 --
 Thomas Viehmann, http://thomas.viehmann.net/


Mathieu Parent



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]