condor_ping - HTCondor Manual

       HTCondor Team

       1990-2024,  Center  for High Throughput Computing, Computer Sciences Department, University of Wisconsin-
       Madison, Madison, WI, US. Licensed under the Apache License, Version 2.0.

                                                  Jan 04, 2025                                    CONDOR_PING(1)

condor_ping attempts a security negotiation to discover whether the configuration is set  such  that  the
       negotiation  succeeds.  The  target of the negotiation is defined by one or a combination of the address,
       pool, name, or type options. If no target is specified, the default target is the condor_schedd daemon on
       the local machine.

       One or more token s may be listed, thereby specifying one or more authorization level to  impersonate  in
       security  negotiation.  A  token is the value ALL, an authorization level, a command name, or the integer
       value of a command. The many command names and their associated integer values will more likely  be  used
       by experts, and they are defined in the file condor_includes/condor_commands.h.

       An  authorization  level  may  be  one  of  the  following strings. If ALL is listed, then negotiation is
       attempted for each of these possible authorization  levels.   Note  that  OWNER  is  no  longer  used  in
       HTCondor, but is kept here for use when talking to older daemons (prior to 9.9.0).
          READ  WRITE  ADMINISTRATOR  SOAP  CONFIG  OWNER  DAEMON  NEGOTIATOR  ADVERTISE_MASTER ADVERTISE_STARTD
          ADVERTISE_SCHEDD CLIENT

       The example Unix command

          $ condor_ping  -address "<127.0.0.1:9618>" -table READ WRITE DAEMON

       places double quote marks around the sinful string  to  prevent  the  less  than  and  the  greater  than
       characters from causing redirect of input and output. The given IP address is targeted with 3 attempts to
       negotiate:  one  at  the  READ  authorization level, one at the WRITE authorization level, and one at the
       DAEMON authorization level.

condor_ping will exit with the status value of the negotiation it attempted,  where  0  (zero)  indicates
       success, and 1 (one) indicates failure. If multiple security negotiations were attempted, the exit status
       will be the logical OR of all values.

       condor_ping - HTCondor Manual

       Attempt a security negotiation to determine if it succeeds

-help  Display usage information

          -version
                 Display version information

          -debug Print extra debugging information as the command executes.

          -configfilename
                 Attempt the negotiation based on the contents  of  the  configuration  file  contents  in  file
                 filename.

          -address<a.b.c.d:port>
                 Target the given IP address with the negotiation attempt.

          -poolhostname
                 Target the given host with the negotiation attempt. May be combined with specifications defined
                 by name and type options.

          -namedaemonname
                 Target the daemon given by daemonname with the negotiation attempt.

          -typesubsystem
                 Target  the  daemon  identified  by subsystem, one of the values of the predefined $(SUBSYSTEM)
                 macro.

          -quiet Set exit status only; no output displayed.

          -table Output is displayed with one result per line, in a table format.

          -verbose
                 Display all available output.

condor_ping [-help|-version ]

       condor_ping  [-debug  ] [-address<a.b.c.d:port>] [-poolhostname] [-namedaemonname] [-typesubsystem]
       [-configfilename] [-quiet|-table|-verbose ] token [token[...] ]