| |
|---|
| | |
|---|
| | |
|---|
| | :Author: Tim Daneliuk (tundra@tundraware.com) |
|---|
| | |
|---|
| | :Version: ``$Id: Deconstructing_Linux_udev_Rules.rst,v 1.127 2013/11/01 13:41:23 tundra Exp $`` |
|---|
| | :Version: ``$Id: Deconstructing_Linux_udev_Rules.rst,v 1.128 2013/11/01 13:46:00 tundra Exp $`` |
|---|
| | |
|---|
| | |
|---|
| | Précis |
|---|
| | ====== |
|---|
| |
|---|
| | ownership and permissions values. This can happen when you have |
|---|
| | slow, crufty networks that take a long time to nail up a |
|---|
| | connection between a server and its ``ldap`` authority. The |
|---|
| | numeric values are always right (unless some genius is in the |
|---|
| | habit of changing them often in ``ldap``). And you'll see the |
|---|
| | habit of changing them often in ``ldap``). You'll see the |
|---|
| | proper user- and group names on your mountpoint when ``ldap`` |
|---|
| | connectivity is established. If you want to know what the numeric |
|---|
| | values for user- and group are, do this:: |
|---|
| | |
|---|
| |
|---|
| | |
tundra
authored
on 1 Nov 2013