cschantz/Linux-Server-Management-Toolkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Use same grep logic as trace eraser for history cleaning

Browse Source 
Simplified to match the exact logic from erase-toolkit-traces.sh:
- Use grep -Ev with pattern matching
- Clean file, clear history, reload, unset HISTFILE
- Then run trace eraser subprocess for logs/files/directory

The key fix is running this in the current shell instead of subprocess.
This commit is contained in:
cschantz
2025-11-11 17:53:19 -05:00
parent ddc72cd9dd
commit dc75ae79fe
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
launcher.sh
+1 -1
View File
@@ -1511,7 +1511,7 @@ main() {
# This ensures the parent shell's history is cleaned # This ensures the parent shell's history is cleaned
GREP_PATTERN="git\.mull\.lol|linux-server-management-toolkit|server-toolkit|launcher\.sh|erase-toolkit-traces" GREP_PATTERN="git\.mull\.lol|linux-server-management-toolkit|server-toolkit|launcher\.sh|erase-toolkit-traces"
# Clean the history file # Clean the history file (same logic as trace eraser)
if [ -f ~/.bash_history ]; then if [ -f ~/.bash_history ]; then
cp ~/.bash_history ~/.bash_history.bak.$$ cp ~/.bash_history ~/.bash_history.bak.$$
grep -Ev "$GREP_PATTERN" ~/.bash_history.bak.$$ > ~/.bash_history 2>/dev/null || true grep -Ev "$GREP_PATTERN" ~/.bash_history.bak.$$ > ~/.bash_history 2>/dev/null || true