#8048: command to gather build report on a platform/hardware combination
---------------------------+------------------------------------------------
Reporter: mvngu | Owner: tbd
Type: enhancement | Status: new
Priority: major | Milestone: sage-4.5.2
Component: misc | Keywords:
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
---------------------------+------------------------------------------------
Comment(by jasonbhill):
I attached a new file. I made the 'useless cat' and other changes. (Thanks
Dave!)
Some more notes:
* cpu throttling: It is easy to determine if a cpu supports throttling,
but can be a pain to determine (across various linux distributions) if it
is enabled. Even from Ubuntu 9.10 to 10.04, this changed, and both are
inconsistent with the Debian installations I've tried. So, I'm not
incredibly optimistic here.
* Getting the sage banner isn't a problem, so long as I know my pwd and
how that relates to the banner's location. I haven't yet assumed that this
script is executed anywhere specific.
* I changed the gcc version command to output the entire output. The
extra lines now included are only copyright info though, and so I'd
question if we'd want them.
* I'll add the netstat command (and/or equivalent).
* diskspace is relatively easy. I'll add that as well.
It looks like the OS-X commands are somewhat straightforward, and the
hardware is much more standardized there. Dave: We have a couple of lists
of relevant Sunos commands... can we develop a single list of what is
useful and what isn't? I have Open Solaris on a machine and so testing
won't be an issue.
John:
* You want to update some of the skynet information you posted before.
The cpu information for at least one of the machines changed (since I
thought 'uniq' would apply 'sort' and it doesn't... meaning that the cores
/cpu-count is off).
* I also added the correct greps to attempt to get information from those
Itaniums. My best guess as to why those topology numbers are so strange is
that those machines may actually accept 4 processors, but only have 2
plugged in. If that's not the case, then it's buggy and there just aren't
enough people using those cpus to make it worth fixing.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/8048#comment:17>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
