LQ Suggestions & FeedbackDo you have a suggestion for this site or an idea that will make the site better? This forum is for you.
PLEASE READ THIS FORUM - Information and status updates will also be posted here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Have we ever discussed having a troubleshooting tool that we could refer users to?
Something like:
./lqdebug.sh --samba-setup
to grab the same four command outputs that we always ask for? Dell and Atlassian have that sort of thing for their products. But a general tool might be nice for the forum.
Last edited by szboardstretcher; 12-13-2016 at 02:36 PM.
Reason: removed guide idea as we already discussed it
I've got a lot of experience putting together troubleshooting flow charts and other job aids for training classes. I would be happy to work with a person or team interesting in putting together some troubleshooting aids.
Very interesting. I'll mock up a basic idea and add it to github. I'll link back when I have something concrete. From there if you are interested, you may freely contribute.
The idea is this,.. "User: I have a problem with my mount point not mounting" "Me: run 'ldebug.sh -s' and copy and paste the contents here."
The contents would have for example, /etc/fstab, /proc/mounts, lvs, pvs, blkid, fdisk -l, and that sort of thing. Very simple and very centralized for anyone to be able to easily run:
Done. Rather than posting 4 different times to get the information that we will eventually need anyway, I'd like to get a complete picture right off the rip.
Thoughts? I figure 'storage' would be the first area. Then maybe 'generalsystem'. Then maybe 'networking'. Maybe 'packagemanager'. Anyway, hope its interesting enough to warrant some collaboration and effort.
Last edited by szboardstretcher; 12-14-2016 at 11:05 AM.
You pulled the webpage, not the script. This is a problem with this sort of thing - seen similar when directing users to download bootinfoscript.
One needs to be very specific with instructions.
(Grin) I said I'm not very experienced with Github. I'll try to educate myself tomorrow.
Oddly enough, when I saw the doctype, I tried to open the file from Firefox and the file-open dialog told me I was trying to open a script and pointed me towards Gedit. I am guessing that was based on the file name. (Moments later) I just verified my guess by copying the file to one with an html extension and opening it in Firefox.
I found the script on my own. It seems to run quite nicely. I do have some ideas for some other information to automate the seeking of which, he said ungrammatically; I think I will work on them and then run them by you. Let me know the best way to do that.
I'll have to bone up on scripting, though; fortunately, I have my Garrels book on scripting on the bookshelf. It's been a while since I wrote anything more complex than my Fluxbox wallpaper script:
Code:
#!/bin/sh
while true; do
# fbsetbg -f -R ~/wallpapers
fbsetbg -f -R ~/Christmas
sleep 30m
Cool. If you haven't used github, it might be worth it to grab an account and learn to use the pull request system. Basically you press 'fork' on this script, make your changes to your own copy of it, then do a pull request which essentially comes back to me and says 'would you like these changes added to the script?'
Its a good way for many of us to work on it.
Or you can suggest them here. Up to you. If there get to be lots of ideas and input we would have to go the github route.
Now,. on the scripting front. If you aren't up to speed on scripting, then you could offer command collections - Since we are really just looking to quickly display relevant information. For example:
Quote:
You: Hey I have some information gathering commands all related to the category "Programs and Packages" here are the commands:
rpm -qa
yum repolist
And I could just add it to a 'Programs and packages' section of the script. Any help is certainly appreciated. Have fun!
I think I shall open a git-hub account and check out some tutorials. I'm sure I'll have questions.
This would be a great opportunity for me to learn more about scripting; I've found one learns best when one has a goal. If I'm not satisfied with my progress, I'll post my suggestions here.
Good catch! Hmmm. I wonder if debian wants the () removed completely... I will spin up a debian instance to test on as well so I can cover Centos/Debian variants at least.
I've also updated the script to remove the wordiness of the $(which) stuff I was doing. Created a tmpfile.. And also added a way to automatically send the output to a pastebin online the -Z switch in the newest version. So running './ldebug.sh -lZ' gets regular output, sends it to a pastebin, and outputs this line:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.