| Mailing List ArchivesAuthenticated access |  | ![[Computer Systems Lab]](http://www.cs.wisc.edu/pics/csl_logo.gif)  | 
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] how to validate Collector and Schedd initilization with the python bindings?
- Date: Tue, 29 May 2018 14:07:37 -0500
- From: Todd Tannenbaum <tannenba@xxxxxxxxxxx>
- Subject: Re: [HTCondor-users] how to validate Collector and Schedd initilization with the python bindings?
On 5/25/2018 4:10 PM, Jose Caballero wrote:
Hi,
naively, one would expect an Exception when doing something like this
          import htcondor
          coll = htcondor.Collector(" a fake collector ")
which is not the case.
Ditto with Schedd( )
What is the best way to test it right after initialization w/o
triggering any real action?
Besides what Jason mentioned, you could use the htcondor.SecMan().ping() 
method, which does indeed throw an exception if the daemon fails to send 
an acknowledgement.
For an example, see
  http://htcondor.org/python_notebook_examples/HOWTO_use_ping.html
Or to grab the jupyter notebook I used for this, grab
  http://htcondor.org/python_notebook_examples/HOWTO_use_ping.ipynb
regards,
Todd
Thanks,
Jose
_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/
--
Todd Tannenbaum <tannenba@xxxxxxxxxxx> University of Wisconsin-Madison
Center for High Throughput Computing   Department of Computer Sciences
HTCondor Technical Lead                1210 W. Dayton St. Rm #4257
Phone: (608) 263-7132                  Madison, WI 53706-1685