CONDOR_TOKEN_REQUEST_LIST(1)

📦
version 25.14.1 · 12 versions
, in fedora 43

✨ NAME ✨

condor_token_request_list — from the HTCondor Manual, section 1, and it's literally here to list all token requests at a remote daemon 💅

🌸 SYNOPSIS 🌸

condor_token_request_list [-pool pool_name] [-name hostname] [-type type] [-json] [-debug]

condor_token_request_list [-help ]

🫶 DESCRIPTION 🫶

Okay so bestie, condor_token_request_list will list all the requests for tokens that are currently queued up at a remote daemon. That's it, that's the job — it's giving "front desk of the token club" energy. This is the tool that lets the administrator actually review those token requests 👑, and heads up, those requests can be approved later by invoking condor_token_request_approve.

Now the vibe check on permissions: if you're an individual with ADMINISTRATOR authorization, you get to see all queued token requests. Otherwise? You only see token requests for your own identity. No peeking at other people's business, periodt 🙈.

By default, condor_token_request_list queries the local condor_collector. But if you specify a combination of -pool, -name, or -type, the tool can request tokens in other pools, on other hosts, or from different daemon types. Mix and match, slay ✨.

💖 OPTIONS 💖

  • -debug — sends debugging information to stderr, based on the value of the configuration variable TOOL_DEBUG. Very "tell me everything" of it 💀
  • -help — display brief usage information and exit. The classic.
  • -name hostname — request a token from the daemon named hostname in the pool. If you don't specify it, the locally-running daemons get used instead.
  • -pool pool_name — request a token from a daemon in a non-default pool, pool_name. Going somewhere fancy 💅
  • -json — causes all pending requests to be printed as JSON objects. Machine-readable, iconic, no notes.
  • -type type — request a token from a specific daemon type, type. If it's not given, a condor_collector is used.

🌈 EXAMPLES 🌈

To list the tokens at the default condor_collector, you literally just do this:

$ condor_token_request_list
RequestId = "4303687"
ClientId = "worker0000.wisc.edu-960"
PeerLocation = "192.0.2.13"
AuthenticatedIdentity = "anonymous@ssl"
RequestedIdentity = "condor@cs.wisc.edu"
LimitAuthorization = "ADVERTISE_STARTD"

RequestedIdentity = "bucky@cs.wisc.edu"
AuthenticatedIdentity = "bucky@cs.wisc.edu"
PeerLocation = "192.0.2.211"
ClientId = "desktop0001.wisc.edu-712"
RequestId = "4413973"

Look at all those requests just sitting there waiting 🍓

⭐ EXIT STATUS ⭐

condor_token_request_list will exit with a non-zero status value if it fails to communicate with the remote daemon or fails to authenticate 😭. Otherwise, it will exit 0. We love a clean exit, we love a happy ending 🎀.

🦋 SEE ALSO 🦋

Go read the whole squad, fr fr.

👑 AUTHOR 👑

Center for High Throughput Computing, University of Wisconsin-Madison

💜 AUTHOR 💜

HTCondor Team

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

Okay that's the whole page, bestie — no crumbs left. This was the CONDOR_TOKEN_REQUEST_LIST(1) page from the HTCondor Manual, dated Oct 16, 2026, and you read the entire thing. Main character energy, honestly 💅✨🫶
📦 where this page comes from