Timeline for safe way to add aliases for another user?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 10, 2018 at 14:25 | answer | added | Kusalananda♦ | timeline score: 0 | |
| Dec 7, 2017 at 15:50 | comment | added | Stephen | What I was thinking is if there's a way to say "if the user which sudo'd to this user = myrealusername, alias xyz." That way it would be guaranteed to only be invoked if it's me running this particular user. | |
| Dec 6, 2017 at 16:17 | comment | added | ilkkachu | Either create a new user for yourself, or put your own aliases & functions in a separate file and load them from there when starting a shell. Really, if you run interactive shells on a system, you do want to have personal configuration files for the shells. (not just aliases but prompts and shell settings too.) | |
| Dec 6, 2017 at 15:23 | comment | added | Stephen | Question based on the other question Richard linked to: How does bash decide if the shell is "interactive"? Couldn't my machine account be running in interactive mode, like for example if a job server logs in under the machine account to run the jobs? | |
| Dec 6, 2017 at 15:18 | comment | added | Richard Neumann | If your scripts aren't explicitely loading ~/.bashrc or set BASH_ENV, you should be fine to add aliases. | |
| Dec 6, 2017 at 15:16 | comment | added | Raman Sailopal | Check the return status of the type command for the aliases in question i.e. "type e" This will tell you whether you can set them up or not. | |
| Dec 6, 2017 at 15:05 | review | First posts | |||
| Dec 6, 2017 at 15:48 | |||||
| Dec 6, 2017 at 15:05 | history | asked | Stephen | CC BY-SA 3.0 |