network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 4 months |
| seen | Feb 12 at 21:17 | |
| stats | profile views | 1 |
|
Jan 9 |
comment |
Using autofs to mount under each users' home directory Have you used scripts before? I get that you have to print the resultant autofs 'file' to stdout, but can it spit stderr to the end-user and read user input with read var (I'm thinking specifically about prompting for credentials, or at least reporting failure)? Or is the script run in a background process somewhere? |
|
Jan 9 |
comment |
Using autofs to mount under each users' home directory This is a matter of clarity in documentation then, I guess: the man line The following special variables will be substituted in the *key and location fields* of an automounter map if prefixed does not apply to the per-user variables that follow the man line autofs provides additional variables that are set based on the user requesting the mount. The script approach might be interesting, though. I'll see if I can wrap my head around coercing the logic into a working script... |
|
Jan 8 |
comment |
Using autofs to mount under each users' home directory Thanks for this. Given autofs provides additional variables that are set based on the user requesting the mount, does that not mean $USER is already understood by autofs to be the guy who just cd'd into the path? Same with $HOME, I'd have thought. Is that the bit I am misunderstanding? Could it be more that the variable substitution cannot take place in the path part of the config file, only in the response part? So I can automount with config: /mydomain /etc/auto.mydomain --timeout=60 but I can't with config: $HOME/mydomain /etc/auto.mydomain --timeout=60? |
|
Jan 8 |
awarded | Student |
|
Jan 8 |
asked | Using autofs to mount under each users' home directory |
