wdel(1) Internet Applications - FTP wdel(1)NAME
wdel - A wget-like program for deleting files on ftp servers
SYNOPSIS
wdel [option]... [URL [file]...]...
DESCRIPTION
Wdel is a free utility that is able to delete files on an ftp server.
Wdel is non-interactive and background-capable. It can delete files or whole directories and is meant to be a robust client even for unsta-
ble connections and will therefore retry to delete a file, if the connection broke.
Wdel supports connections through proxies, allowing you to use it in an environment that can access the internet only via a proxy or to
provide anonymity by hiding your ip-address to the server. For SOCKSv5-proxies Wdel supports also listening mode, allowing you to use
port-mode ftp through a proxy (useful if the remote ftp is behind a firewall or a gateway).
URL-Input-Handling
URLs are recognized by the ftp://-prefix.
Wdel first reads the URLs from the command line, and associates every file with the last URL until a new URL is found (note that this is
different from wput). Then, it reads the --input-file (if any) and parses the URLs in the same way. So you can specify e.g. one URL and
read all filenames from a file.
If there are no explicit filenames given for a singe URL, then the last part of the URL is taken to be the file/directory to be deleted. If
there are filenames, then the last part of the URL is considered to be the directory where these files reside in. Slashes at the end of the
URL or the filename (in case it is a directory to be deleted) are ignored.
OPTIONS
There are no special options introduced by Wdel. All of Wput's options may be supplied, although some will not be of any effect because
they do not apply for the process of deleting files. Please see wput(1) for a description of the options.
SEE ALSO
Many options can be set in a wputrc file. For its documentation consult the sample file provided by Wput.
wput(1) describes all setable options. Not all apply for wdel too though.
AUTHOR
Wdel is written by Hagen Fritsch <fritsch+wdel-man@in.tum.de> and Jan Larres <jan@majutsushi.net>
Hagen Fritsch, Jan Larres 0.6.2 wdel(1)
Check Out this Related Man Page
GFREG(1)GFREG(1)NAME
gfreg - register a Gfarm file, Gfarm file fragments, or a Gfarm directory
SYNOPSIS
gfreg [ -p ] [ -h filesystem-node | -H hostfile | -D domainname ] [ -a architecture ] program ... gfarm-URL
gfreg [ -i ] [ -h filesystem-node | -H hostfile | -D domainname ] localfile ... gfarm-URL
gfreg -N total-num-of-fragments -I fragment-index [ -h filesystem-node | -H hostfile | -D domainname ] localfile ... gfarm-URL
gfreg -r [ -h filesystem-node | -H hostfile | -D domainname ] [ -a architecture ] [ directory | program | localfile ] ... gfarm-URL
DESCRIPTION
The first form copies and registers the program as a Gfarm file gfarm-URL in the Gfarm filesystem. When gfarm-URL is a directory, multiple
programs can be specified. After the registration, the gfarm-URL can be specified as a program name of gfrun(1) and gfmpirun_p4(1). With-
out the -p option, only executable file can be specified. With the -p option, non-executable file can be specified as well. Without the
-a option or the -h option, architecture of the program is assumed to be the same architecture as the client host on that gfreg(1) is exe-
cuted, which is obtained by the Gfarm metaserver.
The second form registers one or more localfiles as a single Gfarm file. Without the -i option, only non-executable file can be specified
as localfile. With the -i option, both excutable and non-executable file can be specified as localfile. The destination filesystem node
will be automatically selected by CPU load average. With any one of -h, -H, -D options, filesystem node can be limited.
The third form registers localfile as a file fragment of a Gfarm file. The total number of fragments and the fragment index are specified
by the -N option and the -I option, respectively. When gfarm-URL is a directory, multiple localfiles can be specified. The destination
filesystemnode will be automatically decided by CPU load average unless any one of -h, -H, -D options is explicitly specified. When the
gfreg command of this form is executed on a filesystem node, the local filesystem node is always selected rather than a remote filesys-
temnode. In this case, -h, -H, -D options help to store files dispersively.
The fourth form registers the directory as a Gfarm directory gfarm-URL, the program or the localfile as a Gfarm file gfarm-URL. If direc-
tory have some sub directories and/or files, they will be registered recursively. The non-executable file localfile will be registered as
a file has one fragment. A non-executable file in the directory will be registered in the same way. When gfarm-URL already exists as a
directory, multiple directories, programs, and localfiles can be specified and they will be registered in gfarm-URL. They can be mixed in
parameteres, while other forms inhibit this manner. If gfarm-URL does not exist, one directory or one program, or one localfile can be
specified and it will be registered as gfarm-URL. Refer to the first form's part above to specify filesystem node thatprogfarms and files
will reside with the -a option or the -h option.
OPTIONS -f overwrites gfarm-URL even if it exits as a Gfarm file.
-? displays a list of command options.
Gfarm 05 April 2006 GFREG(1)