From: Andrew M. <adm...@um...> - 2008-03-27 17:51:07
|
On Mar 27, 2008, at 12:51 AM, Warren Turner wrote: > In the Command File editor, on the command file I tested this with, > the only thing I have listed is one line that says "/Library/ > Preferences/Reason\bData". That's how it should appear. Part of the benefit of special files is that you don't have to create multiple command files for every special file. You put the special entry in the command file--"s ./path/to/ file"--and give it to all the clients who need the special file. The special entry itself is generic; there should be only one entry per special path in the command file. The server determines what the actual special file contents will be when the client requests it, based on how the client was granted access to the server. Say I have two clients, 192.168.0.1 and 192.168.0.2. The config file looks like this: 192.168.0.<1-2> base.K And base.K looks like this: p lfs-base.T n lfs-negative.T s ./etc/fstab Now when 192.168.0.1 connects and wants to download ./etc/fstab, the server notices that the client was allowed access because its IP address matched an entry in the config file. Using that IP address, the server constructs the path to the special file, opening /var/ radmind/special/192.168.0.1/etc/fstab, and sending the contents to the client. When 192.168.0.2 connects, the server opens /var/radmind/ special/192.168.0.2/etc/fstab. Does this clear things up? > Also, while I was testing this with a few different overloads, the > command file I was using got corrupted a number of times. I haven't > searched through the bug reports, but does anyone know if this > common when using the GUI? Thanks. Search the bug reports first. If you don't find a report that describes your problem, please post a new one, including steps to reproduce the unexpected behavior. andrew |