5 ms·

When I used to admin Windows servers we had production’s desktop background set to red, that worked well, especially when you had multiple remote desktop sessio

by davedx 4y ago

When I used to admin Windows servers we had production’s desktop background set to red, that worked well, especially when you had multiple remote desktop sessions open. Wonder if that’s doable for non-GUI enabled Linux servers

t-3 4y ago
The standard way is to set PS1 (the commandline prompt text) to indicate the environment. With escape codes, you can pretty trivially get some flashing red text telling you to be careful.
- hobs 4y ago
  If used properly the -Confirm parameter in powershell can also have you change the impact level in your environment and ask for confirmation on things that in dev would not be cared about. Also its underused but the just in time access stuff where you can grant users subsets of permissions (again, per environment) is also pretty impressive.
- formerly_proven 4y ago
  A not-so standard way is to output a banner via shrc (instead of putting it in the motd, which the ssh daemon will only output for interactive sessions) - which incidentally will also break pretty much all tools using SSH as a transport (scp, rsync, among others).
linschn 4y ago
I use the color of tmux's bar to the same effect.
qalmakka 4y ago
That was also the case in very old Linux distros when you logged on X as root. I clearly remember something like Fedora or Mandriva doing exactly that - note that graphically logging in as root on a Unix system is not a great idea though, most GUI software isn't designed for it.
- 867-5309 4y ago
  the terminal background could be changed from black to red
- detaro 4y ago
  SuSE had bright red background with exclamation mark signs and bomb icons
- NathanielK 4y ago
  Other applications can do it too. I recall the Gnome file browser having a big red warning banner if you decided to launch it with gksudo.
orev 4y ago
It’s pretty easy to insert colors into to prompt using conditional logic in things like bashrc. You can also add them to other system tools like ‘screen’ and (I assume) ‘tmux’. People can override them if they want, but it’s a good starting default (and people rarely override defaults on a fleet of servers).
iso1631 4y ago
20 years ago our live/test/dev solaris + linux environments had different coloured prompts (green/yellow/red) Hasn't really been best practice in many workflows to connect to servers at all for a decade
yencabulator 4y ago
My prompt only includes username if it's not the usual one, and it's on an orange-red background if it's root. Similarly, my prompt doesn't include the host when I'm logged in normally, adds it when I'm in a shell via sudo/doas, and colors it when I'm logged in via SSH.
deleted 4y ago
[deleted]

by davedx 4y ago

t-3 4y ago

The standard way is to set PS1 (the commandline prompt text) to indicate the environment. With escape codes, you can pretty trivially get some flashing red text telling you to be careful.

hobs 4y ago
If used properly the -Confirm parameter in powershell can also have you change the impact level in your environment and ask for confirmation on things that in dev would not be cared about. Also its underused but the just in time access stuff where you can grant users subsets of permissions (again, per environment) is also pretty impressive.
formerly_proven 4y ago
A not-so standard way is to output a banner via shrc (instead of putting it in the motd, which the ssh daemon will only output for interactive sessions) - which incidentally will also break pretty much all tools using SSH as a transport (scp, rsync, among others).

linschn 4y ago

I use the color of tmux's bar to the same effect.

qalmakka 4y ago

That was also the case in very old Linux distros when you logged on X as root. I clearly remember something like Fedora or Mandriva doing exactly that - note that graphically logging in as root on a Unix system is not a great idea though, most GUI software isn't designed for it.

867-5309 4y ago
the terminal background could be changed from black to red
detaro 4y ago
SuSE had bright red background with exclamation mark signs and bomb icons
NathanielK 4y ago
Other applications can do it too. I recall the Gnome file browser having a big red warning banner if you decided to launch it with gksudo.

orev 4y ago

It’s pretty easy to insert colors into to prompt using conditional logic in things like bashrc. You can also add them to other system tools like ‘screen’ and (I assume) ‘tmux’. People can override them if they want, but it’s a good starting default (and people rarely override defaults on a fleet of servers).

iso1631 4y ago

20 years ago our live/test/dev solaris + linux environments had different coloured prompts (green/yellow/red) Hasn't really been best practice in many workflows to connect to servers at all for a decade

yencabulator 4y ago

My prompt only includes username if it's not the usual one, and it's on an orange-red background if it's root. Similarly, my prompt doesn't include the host when I'm logged in normally, adds it when I'm in a shell via sudo/doas, and colors it when I'm logged in via SSH.

deleted 4y ago

[deleted]