Marc Muehlfeld wrote:
Hi,
I saw a interesting behavier when I use amadmin to force a level 0. While
a force to the root file system just set this one to level 0:
# amadmin KDD force genome /
amadmin: genome.mr.lfmg.de:/ is set to a forced level 0 at next run.
a force to a mountpoint that contains other, forces recurive all other
below that one to level 0,too (what I don't wanted and don't expected):
# amadmin KDD force genome /shares
amadmin: genome.mr.lfmg.de:/shares is set to a forced level 0 at next run.
amadmin: genome.mr.lfmg.de:/shares/Abteilungen is set to a forced level 0
at next run.
amadmin: genome.mr.lfmg.de:/shares/IT is set to a forced level 0 at next run.
...
Bug, Feature, wrongly used,...?
Can't say for sure, but suppose you tried "/shares/" instead of
"/shares"? So,
# amadmin KDD force genome /shares/
---------------
Chris Hoogendyk
-
O__ ---- Systems Administrator
c/ /'_ --- Biology & Geology Departments
(*) \(*) -- 140 Morrill Science Center
~~~~~~~~~~ - University of Massachusetts, Amherst
<[EMAIL PROTECTED]>
---------------
Erdös 4
