-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
grml-hwinfo: Include some more error outputs #12
Comments
Otherwise executing `parted -s /dev/nvme0n1 print` might throw something like this for empty disks: Error: /dev/nvme0n1: unrecognized disk label Related to #12
Otherwise executing lspci might spill something like: # lspci -vvnn > /dev/null pcilib: sysfs_read_vpd: read failed: No such device Which according to https://bugzilla.kernel.org/show_bug.cgi?id=199467 isn't an "actual" error, but there is just no VPD EEPROM present. But as long as it shows up on stderr, it behaves like an error, so let's also tread it like an error. :) Related to #12 Thanks: Darshaka Pathirana for the bug report
So I also stumbled upon the The The
Either you report it to stderr because it's an error or not? ;) Instead I fully agree with:
So for the time being let's also report But I agree also with @jkirk's:
Though this needs further redesign of how grml-hwinfo works, maybe let's discuss this before closing this issue? |
Quick idea: What about a third(?) "full" log file for every output where we put 'stdout' and 'stderr' in one file? |
Sorry, don't understand your idea or how that exactly should look like 🤔 |
I meant something like this:
|
That would be nice, though AFAICT this only works in zsh (thanks to multios), but not under bash 😞 |
Some more error output is missing:
I was using an older Grml daily. So, the
sdparm
problem was fixed in #10, but we should include the error outputs oflspci
andparted
and most probably some other tools.I also think that putting the error output in a separate file is problematic, as one can not see where the error actually occurs.
But on the other hand look at this:
The output of
pcilib: sysfs_read_vpd: read failed: No such device
is "somewhere else":FTR,
pcilib: sysfs_read_vpd: read failed: No such device
is not an "actual" error, there is just no VPD EEPROM present: https://bugzilla.kernel.org/show_bug.cgi?id=199467(But this is a bug and this isn't handled well in pcilib.)
The text was updated successfully, but these errors were encountered: