Sponsored Content
The Lounge What is on Your Mind? Announcement: New Discourse Site to Go Live this Weekend Post 303045426 by sea on Friday 20th of March 2020 10:57:02 AM
Old 03-20-2020
Wait, we'll get a new url?
Or will 'this page' just move to an archive dir?
 

5 More Discussions You Might Find Interesting

1. Web Development

Setting up Development and Live web site environment

Hi, I am fairly new to unix so please go easy on me.. I have a VPS on which I would like to setup a development and live web site environment and can't seem to work out what is the best technique for doing so. I would like to be able to mirror the live site and have a "check out" and... (0 Replies)
Discussion started by: ciantrius
0 Replies

2. IP Networking

How to establish site to site vpn - Linux machine and cisco asa?

Hi, I am trying to establish vpn between my linux server and cisco asa at client side. I installed openswan on my cent os. Linux Server eth0 - 182.2.29.10 Gateway - 182.2.29.1 eth1 - 192.9.200.75 I have simple IPtables Like WAN="eth0" LAN="eth1" (0 Replies)
Discussion started by: ashokvpp
0 Replies

3. IP Networking

Does cisco 1921 router support site to site VPNs using IPSec?

Q: "Does Cisco 1921 router support,, act as an endpoint for, site to site VPNs using IPSec? If so, how many? " A: If you get the Cisco 1921/k9 with the security services bundle then it will have built in security features. Cisco, typically includes IP Sec tunnels I believe as part of that... (0 Replies)
Discussion started by: Ayaerlee
0 Replies

4. IP Networking

IPSec Openswan Site to Site VPN - Big Pain

Hi @all, I try to connect 2 LANs with IPSec/Openswan LAN 1: 192.168.0.0/24 LAN 2: 192.168.1.0/24 This is my Config: conn HomeVPN # # Left security gateway, subnet behind it, nexthop toward right. left=192.168.1.29 ... (1 Reply)
Discussion started by: bahnhasser83
1 Replies

5. What is on Your Mind?

Update: UserCP Screeching Frog 0.7641 - Changed Live Chat to Live Updates

Update: UserCP Screeching Frog 0.7641 - Changed Live Chat to Live Updates In this version of the UserCP, I have changed "Live Chat" to "Live Updates" by disabling the ability to post in the "live chat" area and changed the name to "Live Updates" The reason for this change is that experienced... (6 Replies)
Discussion started by: Neo
6 Replies
condor_cold_stop(1)					      General Commands Manual					       condor_cold_stop(1)

Name
       condor_cold_stop reliably - shut down and uninstall a running Condor instance

Synopsis
       condor_cold_stop -help

       condor_cold_stop[-force]  [-basedir  directory]	[-localdir directory] [-runlocalconfig file] [-cleaninstall] [-cleanlocal] [-stop] [-loga-
       rchive archive] [-spoolarchive archive] [-execarchive archive] [-filelock] [-pid] [-artifact file]  [-nogurl]  [-globuslocation	directory]
       -configfile file

Description
       condor_cold_stop  reliably  shuts  down	and uninstall a running Condor instance. This program first uses condor_local_stopto reliably shut
       down the running Condor instance. It then uses condor_cleanup_localto create and store archives of the  log ,  spool , and  execute  direc-
       tories. Its last task is to uninstall the Condor binaries and libraries using cleanup_release.

Options
       -artifact file

	  Uses fileas the artifact file to determine whether the condor_masterdaemon is still alive.

       -basedir directory

	  Directory where the Condor installation can be found. When not specified, the current working directory is assumed.

       -cleaninstall

	  Remove  the Condor installation. If none of the options -cleaninstall, -cleanlocal, or -stopare specified, the program behaves as though
	  all of them have been provided.

       -cleanlocal

	  The program will remove the  log ,  spool ,  exec directories for this Condor instance. If none of the options -cleaninstall,  -cleanlo-
	  cal, or -stopare specified, the program behaves as though all of them have been provided.

       -configfile file

	  The  same configuration file path given to condor_cold_start. This program assumes the file is in the installation directory or the cur-
	  rent working directory.

       -execarchive archive

	  The program will create a tar'ed and gzip'ed archive of the  execute directory and stores it as archive. The archivecan be a	file  path
	  or a grid-ftp url.

       -filelock

	  Determine whether the condor_masterdaemon has exited using a file lock undertaker. This option must match the corresponding option given
	  to condor_cold_start.

       -force

	  Ignore the status of the condor_schedddaemon (whether it has jobs in the queue or not) when shutting down Condor.

       -globuslocation directory

	  The directory containing the Globus installation. This option is required if any of the options  of  the  form  -*archiveare	used,  and
	  Globus is not installed in  /opt/globus .

       -localdir directory

	  Directory  where  the   log  ,  spool , and  execute directories are stored for this running instance of Condor. Required if the -clean-
	  localoption is specified.

       -logarchive archive

	  The program will create a tar'ed and gzip'ed archive of the  log directory and stores it as archive. The archivecan be a file path or  a
	  grid-ftp url.

       -nogurl

	  Do not use globus-url-copyto store the archives. This implies that the archives can only be stored on mounted file systems.

       -pid

	  Determine  whether  the  condor_masterdaemon	has  exited using a unique process id undertaker. This option must match the corresponding
	  option given to condor_cold_start.

       -runlocalconfig file

	  Bind fileinto the configuration used by this instance of Condor. This option should the one provided to condor_cold_start.

       -spoolarchive archive

	  The program will create a tar'ed and gzip'ed archive of the  spool directory and stores it as archive. The archivecan be a file path	or
	  a grid-ftp url.

       -stop

	  The  program	will  shut down this running instance of Condor. If none of the options -cleaninstall, -cleanlocal, or -stopare specified,
	  the program behaves as though all of them have been provided.

Exit Status
       condor_cold_stop will exit with a status value of 0 (zero) upon success, and non-zero otherwise.

Examples
       To shut down a Condor instance on the target machine:

       % condor_cold_stop  -configfile condor_config.mobile

       To shutdown a Condor instance and archive the log directory:

       % condor_cold_stop  -configfile condor_config.mobile 

	-logarchive /tmp/log.tar.gz

See Also
       condor_cold_start(on page ), filelock_undertaker(on page ), uniq_pid_undertaker(on page ).

Author
       Condor Team, University of Wisconsin-Madison

Copyright
       Copyright (C) 1990-2012 Condor Team, Computer Sciences Department, University of  Wisconsin-Madison,  Madison,  WI.  All  Rights  Reserved.
       Licensed under the Apache License, Version 2.0.

       See the Condor Version 7.8.2 Manualor http://www.condorproject.org/licensefor additional notices. condor-admin@cs.wisc.edu

								  September 2012					       condor_cold_stop(1)
All times are GMT -4. The time now is 12:43 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy