| 1 |
On 01/02/2015 17:07, Peter Humphrey wrote: |
| 2 |
> On Sunday 01 February 2015 14:17:04 Alan McKinnon wrote: |
| 3 |
>> On 01/02/2015 02:18, Adam Carter wrote: |
| 4 |
>>> If you've su'd to root, try 'su -' instead. |
| 5 |
>>> |
| 6 |
>>> Thank you, that was it? |
| 7 |
>>> What difference does it make and why on some boxes it has to be "su |
| 8 |
>>> -" and on others simple "su" works. |
| 9 |
>>> |
| 10 |
>>> Read 'man su'. I dont really understand this stuff well enough, but a |
| 11 |
>>> 'login shell', that is, one started by /bin/login, is setup with a |
| 12 |
>>> different environment to a shell that's started by su (or by, say, |
| 13 |
>>> cron). This is why a shell command or script may work for you when |
| 14 |
>>> you're logged in, but not if you run it from cron. I'm sure other's can |
| 15 |
>>> explain it more correctly and fully. |
| 16 |
>> |
| 17 |
>> This stuff is complex the first time you run into it. |
| 18 |
> |
| 19 |
> --->8 |
| 20 |
> |
| 21 |
> [Much good advice] |
| 22 |
> |
| 23 |
> I think of it simply like this: "su" switches user, and that's all; "su -" |
| 24 |
> gives you the full environment of the user you switch to. |
| 25 |
> |
| 26 |
|
| 27 |
Indeed, that is the heart of it. |
| 28 |
|
| 29 |
Your version above is perfect for the tl;dr people :-) |
| 30 |
|
| 31 |
-- |
| 32 |
Alan McKinnon |
| 33 |
alan.mckinnon@×××××.com |
Archives