Menu
▾
▴
[ net-snmp-Bugs-1838427 ] Ubuntu shift /bin/sh /bin/bash bash
|
From: SourceForge.net <no...@so...> - 2009-03-18 18:45:26
|
Bugs item #1838427, was opened at 2007-11-26 04:11 Message generated for change (Comment added) made by sf-robot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=112694&aid=1838427&group_id=12694 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: configure Group: linux >Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: "Quigs" (triplespaces) Assigned to: Nobody/Anonymous (nobody) Summary: Ubuntu shift /bin/sh /bin/bash bash Initial Comment: root@lux-master:/etc/snmp# net-snmp-config --create-snmpv3-user -ro -a "<censored>" venice adding the following line to /var/lib/snmp/snmpd.conf: createUser venice MD5 "<censored>" DES adding the following line to /usr/share/snmp/snmpd.conf: rouser venice shift: 485: can't shift that many dash can't handle the number of shift in the shell script. Changing it to use /bin/bash makes it work fine :-) Issue found on edgy/feisty/gutsy. Submitting here so someone can tell me if it's an ubuntu specific issue or not. https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/104738 ---------------------------------------------------------------------- >Comment By: SourceForge Robot (sf-robot) Date: 2009-03-18 18:45 Message: This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 180 days (the time period specified by the administrator of this Tracker). ---------------------------------------------------------------------- Comment By: Dave Shield (dts12) Date: 2008-07-30 17:37 Message: Logged In: YES user_id=88893 Originator: NO There was a fix to improve the /bin/sh compatability which was applied to the development code some time ago. I've just back-ported this change to the active branches, so it should be present in the upcoming 5.4.2 release. It would be useful hear whether this change (SVN revision 17139) does actually fix this problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=112694&aid=1838427&group_id=12694 |