Page History
Client Admin
The client admin tools allow a user to do some file/directory operations in Xrootd: stat, rm, mkdir, checksum,.....
There are different tools:
...
xrdls
...
xrdcmd Client admin tools
xrdcmd is wrapped around xrd.pl. It sets up the environment (LD_LIBRARY_PATH and PERL5LIB), If this environment is set by other means one could call xrd.pl instead of xrdcmd.
xrdcmd implements currently only a subset of all client admin tools. The location of the script is:
~glastdat/bin/xrdcmd
To get more information run : ~glastdat/bin/xrdcmd -h
Examples> xrdcmd -s glast-rdr stat /glast/wilko/f1
size 37 onDisk 1 flags 48 modTime 1178659009 Tue May 8 14:16:49 2007 /glast/wilko/f1
> xrdcmd -s sulky48 dir /glast/mc
DC2
ServiceChallenge
junk
...
something similar to ls
Xrootd does not provide the directory listing (ls) semantics as a file system does.
The xrdls is a command line tool that looks a little bit like an ls. By defaults it
loops over all xrootd data servers and obtains a directory listing for each of them.The usage is:
| Panel | ||
|---|---|---|
| ||
xrdls [-l] [dataserver] directory
|
dataServer directory It is implemented by using the standard unix ls command together with the
xrootd preload library. Using the long listing the user and group name are
not meaningful. The time shown is the mtime.
Below are some examples
| Panel | ||
|---|---|---|
| ||
> xrdls | ||
| Code Block | ||
|
> xrdls /glast/mc ==listing from server sulky02
TonyTest junk
from server sulky47
ServiceChallenge junk
from server sulky48
ServiceChallenge TonyTest junk | ||
junk |
| No Format | ||
|---|---|---|
| ||
>xrdls -l /glast/mc
==listing from server sulky02
total 4
drwx------ 1 wilko ec 1536 Aug 2 15:38 ServiceChallenge
drwx------ 1 wilko ec 512 Jun 17 13:39 TonyTest
drwx------ 1 wilko ec 512 May 15 16:36 junk
==listing from server sulky47
total 3
drwx------ 1 wilko ec 512 Jan 8 2007 DC2
drwx------ 1 wilko ec 512 May 3 09:54 ServiceChallenge
drwx------ 1 wilko ec 512 Feb 28 09:13 junk
==listing from server sulky48
total 5
drwx------ 1 wilko ec 512 Jan 8 2007 DC2
drwx------ 1 wilko ec 1536 Jul 27 17:28 ServiceChallenge
drwx------ 1 wilko ec 512 Jun 17 13:39 TonyTest
drwx------ 1 wilko ec 512 May 16 18:15 junk
|
| No Format | ||
|---|---|---|
| ||
> xrdls -l sulky02 /glast/wilko ==listing from server sulky02 ls: root://sulky02//glast/wilko/n2.root: No such file or directory total 1027 -rw------- 1 wilko ec 0 Aug 9 23:36 DIR_LOCK -rw------- 1 wilko ec 10240 Aug 9 23:35 n1.root -rw------- 1 wilko ec 0 Aug 9 23:34 n1.root.lock -rw------- 1 wilko ec 0 Aug 9 23:35 n2.root.lock -rw------- 1 wilko ec 1037312 Aug 9 23:36 new.root -rw------- 1 wilko ec 0 Aug 9 23:35 new.root.lock drwx------ 1 wilko ec 512 Aug 2 10:23 test |
This example shows a few thinks.
- The line
ls: root://sulky02//glast/wilko/n2.root: No such file or directory
means that there is a link in the directory and the link target (which is the file in the cache) is missing and therefore the stat of the file fails (like ls -lL would do). - There is one special file DIR_LOCK and files with the extensions .lock. These files used by the xrootd to manage a the cache file system and keep track if files have been migrated to HPSS. These files must not be used or removed.