Table of Contents

NAME

qdel - Delete or signal one ore more NQS requests

SYNOPSIS

qdel [ -k ] [ -signo ] [ -u user-name ] request-id ...

DESCRIPTION

The lsNQS version of the NQS command of the same name. lsNQS allows you to use NQS commands to work with the load sharing batch system, lsbatch(1) . qdel deletes or sends a signal to the NQS requests that have been submitted to lsbatch and whose request-ids are listed on the command line.

An lsNQS request is always uniquely identified by its request-id, regardless of which machine it has been dispatched to by lsbatch. The request-id of any NQS request is displayed when the request is first submitted, unless the silent mode of operation for the given lsNQS command was specified (see qsub(1) ). You can also obtain the request-id of any request through the use of the qstat(1) command.

OPTIONS

-k Sends the signal SIGKILL to all requests that have request-ids listed on the command line. This causes a receiving request to exit and be deleted. In the absence of this and the -signo flags, qdel will not delete a running NQS request.

-signo
Sends the specified signal, instead of the default SIGKILL signal, to all requests that have request-ids listed on the command line. signo can be either a signal number or a signal name. The signal names are as given in /usr/include/signal.h, stripped of the common SIG prefix. To delete or signal an NQS request, you must be the owner (that is, the submitter of the request) or the superuser.

-u user-name
Deletes or signals requests owned by the user whose account name is user-name. Normally, you can only signal or delete your own requests. Only the lsbatch administrator is allowed to delete or signal a request submitted by another user.

CAVEATS

When an NQS request is signaled by the methods discussed above, the proper signal is sent to all processes comprising each qualifying NQS request that are in the same process group. Whenever an NQS request is spawned, a new process group is established for all processes in the request. However, if one or more processes of the request successfully executes a setpgrp (2) system call, such processes do not receive any signals sent by the qdel(1) command. This can lead to ``rogue'' request processes that must be killed by other means such as the kill(1) command.

SEE ALSO

qsub(1) , qstat(1) , kill(1) , setpgrp(2) , signal(3c) , lsbatch(1)


Table of Contents