Journalctl -b shows only the log of current boot On 22 mars 2014 11:09:48 UTC+01:00, Jean-Claude Vanier <[email protected]> wrote: >Maybe "systemd boot log" is enough? However, it can be rather heavy. > > >2014-03-22 8:36 GMT+01:00 Alexander Khryukin <[email protected]>: >> You forgot dmesg >> >> 22 марта 2014 г. 9:44 пользователь "Blackcrack" ><[email protected]> >> написал: >> >>> Hi, >>> >>> very niiice idea, should installed as default Application ! >>> maybe later with graphical thing if anyone/anything crash, start >this >>> script and ask the user >>> wi they want sending it in to the Cookers (edit it automatic on an >text >>> field and let show >>> the users what be sending , under all, an button with >"cancel/send/save as >>> txt /" >>> and over it an clean Textfield for writing the bugreport in Users >word's >>> (humanwriteable.. 2 textfiels, one with the collecting informations, >one >>> for human writeable). >>> Maybe in the bash the possible with the command "tc.bugreport" or/ >and >>> "tc.hardwareinfo" >>> or something for have a possible to buildup an hardware-database >from all >>> ! >>> If exist an Gui/grafical tc.bugreport, want be possible for the >testers >>> for easy testing on >>> an Hardware and can start the tc.bugreport and writing in what's >they are >>> done , >>> if the system work well and what's have be seen .. >>> >>> therewith mus be of course, a functioning sendmail-system on it >>> and an well working network configuration, what it is now :) >>> so, only need an working sendmail-system and an gui for you script. >>> for have the possible behind the installation, on first login as >user >>> XXXXX >>> make F2 and typing in "tc.bugreport" >>> you see ? and there can include all what's was on the installation + >you >>> logs and >>> things who you need or you are need as programmers, >>> maybe create an new mailinglist "om-bugreports" >>> showable by all poples ... to know, what's was see and reportet and >which >>> engines running :) >>> this can collecting by db as harware-database and many other things >.. >>> >>> you scripts be an very nice start ! whant be crewl, if you makeing >it as >>> programm >>> with graphical interface for all testers and users ! as >"tc.bugreport" >>> >>> my 2cents :) >>> >>> best regards >>> Blacky >>> >>> >>> Am 21.03.2014 22:55, schrieb Tomasz Paweł Gajc: >>> >>> I've created a simple shell script that will help in a bug fixing. >It is >>> called omv-bug-report. >>> >>> To install it please run: >>> urpmi omv-bug-report >>> >>> This will install in /usr/bin/omv-bug-report.sh a simple shell >script that >>> gathers informationf form: >>> 1. various config files in /etc/* >>> 2. various /proc entries >>> 3. grub configuration >>> 4. lspcidrake output >>> 5. lsusb output >>> 6. dmidecode output >>> 7. systemd --failed >>> 8. journalctl -b >>> 9. rpm -qa >>> 10. gcc version >>> >>> and pack it into omv-bug-report.log.xz. This file should be attached >to >>> any >>> bugreport, just to speed up things and do not wait for a response of >>> bugreporter to provide more detailed information. >>> >>> I've spec a few minutes on this and adapted nvidia-bug-report.sh to >OMV >>> specific environment. Feel free to adjust it more. >>> >>> >>> >>> >>> >>> >> >> >>
-- Envoyé de mon téléphone Android avec K-9 Mail. Excusez la brièveté.
