Useful tips and tricks
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
Can sort these out into their own issues/articles later:
-
Template
.bashrclocation:/etc/skel/.bashrc -
Discover non-essential processes on login:
alias proclist='ps -eo user,pid,ppid,pcpu,pmem,stat,start_time,etime,cmd --sort=-pcpu,-pmem \ | egrep -v " 0.[0-9] 0.[0-9] " \ | egrep -v "auditbeat|metricbeat|vscode|gnome-shell|desktop|firefox|slideshow" \ | egrep -v " [0-9] 0.[0-9]" \ | egrep -v "rsync|polkitd|sftp-server|notty|screensaver|mmfsd|atom"' -
Terminal direct messaging:
user=...; for term in $(w $user | grep $user | awk '{print $2}') do echo "Please do not run jobs on the login node.\nPlease contact support@listserv.uab.edu for assistance." | write $user $term done
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the tips in issue #23, including the /etc/skel/.bashrc location, the proclist alias, and the terminal messaging commands. Split the material into focused issues or articles, with each resulting document clearly explaining its purpose and usage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash, shell
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100