Use GNU Screen for persistent sessions on Slackware

1. When to use it

Ideal for build queues, log tails, and remote maintenance you do not want to lose halfway through.

2. Base setup

printf 'defscrollback 5000\nhardstatus alwayslastline\n' > ~/.screenrc
screen -S admin -d -m tail -f /var/log/messages
screen -S build

Adjust host names, IPs, interfaces, paths, and versions to the real system before making the change persistent.

3. Quick verification

screen -ls
screen -r admin
screen -r build

Confirm that the output matches the expected state before considering the intervention complete.

4. Operational notes

Use clear session names so that even days later you immediately know what each shell is doing.

Quick checklist

[ ] Steps completed\n[ ] Config updated\n[ ] Tests executed\n[ ] Rollback ready\n[ ] Logs checked

Back to Linux HowTo