collector's uuid.py cannot call ifconfig on Solaris

RESOLVED FIXED

Status

Socorro
General
--
enhancement
RESOLVED FIXED
10 years ago
6 years ago

People

(Reporter: Samuel Sidler (old account; do not CC), Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Reported by erik.j.pearson, Sep 25, 2007

What is the problem?

Ifconfig on Solaris behaves somewhat differently than what the socorro
collector expects:

1.  You cannot call "ifconfig" by itself; this generates a usage error. 
You can call "ifconfig -a" to report all interfaces.

2.  If a non-superuser runs ifconfig, the MAC address (ether:) will NOT be
reported.  It is reported when run by superusers.  (Users can find it via
"arp -a", but you need to do some sifting.)

What is the expected behavior? What happens instead?

A usage is generated in apache's error.log file.  Even if fixed, a
non-superuser will run into  issue 2 .

What version of the product are you using, and on what OS?

Socorro revision 249, Solaris 9 (SunOS 5.9)

Please provide any additional information below.
 
--

Comment 1 by ted.mielczarek, Sep 25, 2007

Had to look at the source to clarify where this is called.  I don't think sayrer
actually wrote uuid.py, but I don't know where he got it from.


Summary: collector's uuid.py cannot call ifconfig on Solaris
Cc: sayrer

--

Comment 2 by sayrer, Sep 25, 2007

http://zesty.ca/python/uuid.py
Low priority.
Severity: normal → enhancement
Target Milestone: --- → Future
Target Milestone: Future → ---
we've switched to random uuids instead of ones that depend on the host's IP address.  Specifically, we call uuid4 instead of uuid1.  uuid4 does not try to invoke ifconfig.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
(Assignee)

Updated

6 years ago
Component: Socorro → General
Product: Webtools → Socorro
You need to log in before you can comment on or make changes to this bug.