On 02/04/2015 09:57 PM, Brendan Kearney wrote:
On Wed, 2015-02-04 at 10:31 -0500, brendan kearney wrote:
A lot to chew on here. Seems I may need to rethink my approach for different scenarios. Will do so and reply in a bit.
As for docs, anything is better than nothing. If there is something existing, that will suffice if you can provide links, etc.
Thanks
Brendan
On Feb 4, 2015 3:42 AM, "Ian Kent" ikent@redhat.com wrote: On Wed, 2015-02-04 at 14:06 +0800, Ian Kent wrote: > On Tue, 2015-02-03 at 15:47 +0100, Jakub Hrozek wrote: > > On Tue, Feb 03, 2015 at 09:21:10AM -0500, Brendan Kearney wrote: > > > On Mon, 2015-02-02 at 14:08 +0100, Jakub Hrozek wrote: > > > > On Mon, Feb 02, 2015 at 06:50:12AM -0500, Dmitri Pal wrote: > > > > > On 02/02/2015 01:52 AM, Jakub Hrozek wrote: > > > > > >On Sun, Feb 01, 2015 at 11:17:02AM -0500, Brendan Kearney wrote: > > > > > >>On Sat, 2015-01-31 at 19:01 -0500, Dmitri Pal wrote: > > > > > >>>On 01/31/2015 12:23 PM, Brendan Kearney wrote: > > > > > >>>>i want to have an automount configured so that > > > > > >>>>nas.bpk2.com:/export/music is mounted on /home/<username>/Music. i want > > > > > >>>>to use the HOME variable, but several attempts have not gotten the job > > > > > >>>>done. i have tried $HOME/Music, ${HOME}/Music, and {$HOME}/Music, and > > > > > >>>>none have worked. > > > > > >>>> > > > > > >>>>what is the correct way to use a variable with AutoFS and SSSD? i have > > > > > >>>>used the hard values to get things working for my id, but want to have > > > > > >>>>this work for all users. > > > > > >>>> > > > > > >>>>dn: > > > > > >>>>automountKey=/home/brendan/Music,automountMapName=auto.shares,cn=autofs,ou=Daemons,dc=bpk2,dc=com > > > > > >>>>automountinformation: nas.bpk2.com:/export/music > > > > > >>>>automountkey: /home/brendan/Music > > > > > >>>>description: music > > > > > >>>>objectclass: automount > > > > > >>>>objectclass: top > > This is a direct mount map entry. > You can't use the wildcard key in a direct mount key. > > Oddly enough I suspect you could use the & substitution in the mount > location but that's generally not useful because it would replace the > whole path (the entire key) at it's occurrence in the mount location. > > You can't use macros in lookup keys with them (or indirect mounts) > either because the path is used as the lookup key. > > I know you think that using the information about the requesting could > be used but it's not as simple as that. > > The problem is that multiple processes could request a mount at the same > time, resulting in a queue waiting for mount completion, and the user > information that is returned will be that of the process that originally > triggered the mount and so might not be what you'd expect. There's no > straight forward way to fix that.
And, now that I think about it, there's another reason macros aren't used in direct mount keys. At startup the keys in direct mount maps are used to create trigger mounts for later automounting. That's the only way direct mounts can be done so there's no way to do macro substitution, even if we wanted to, of macros that don't have an already known value. Ian _______________________________________________ sssd-users mailing list sssd-users@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/sssd-usersi just did some reading through man pages and i find no limitations or constraints around the use of variables in direct mappings. can you provide the documentation source you are working from? i want to read through it and better understand the logic about what can and cant be done when using direct vs indirect mappings.
Adding Ian back.
sssd-users mailing list sssd-users@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/sssd-users