 |
 |
On Thu, 13 Jan 2005, Ian Stokes-Rees wrote: > I'm sure that LDAP query above is as familiar as the back of your hand > ... one of my favourite things about LDAP is how intuitive it is to use. Yes, it's really easy after the first few thousand times :) However, I still had to check the syntax when I wanted to give atlas a list of SEs running low on space, it seems you can filter with <= but not < . (Incidentally, one of them is Manchester, so they may want to take a look too ...) > I think there is *some* path, but I don't think it means anything. It's the path on the SE, but it generally isn't visible from the WNs. > So it isn't really possible to see what files a particular VO has on a > particular SE? That's not really a well-defined question, what do you mean by "see" (and "file" for that matter :)? If you mean an ls-type listing, as I said earlier I think you can do it with rfdir from the WN, something like rfdir -R <se.host.name>:<se-path>/<vo-name> > Could it be that users haven't yet figured out how to properly use the > data management system and therefore haven't realised that they don't > have "regular" NFS access to the close SE? Well, that's one way to look at it. I think what most people do is copy files to the working directory and then open them there. However, that has the problem that we still don't have any solution for space management on WNs, and it may also be less efficient. I've suggested re-instating NFS-type access read-only, it's writes which really cause the problems, but unless people demand it I doubt that it will happen. Stephen