Sponsored Content
Operating Systems SCO SCO OpenServer 5.0.4 Media Needed Post 302905281 by flako on Tuesday 10th of June 2014 04:59:31 PM
Old 06-10-2014
if you are migrating to 5.0.7 I can help.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

SCO Openserver 6.0

Hi guys, I just got this new 6.0 version and i'm trying to setup a remote office to telnet to this server running sco 6.0, in previous version all i have to do is add this file under /etc/rc2.d call S99route and put the gate in that file and that was it, for some reason in 6.0 it does not... (1 Reply)
Discussion started by: josramon
1 Replies

2. SCO

Looking for openserver 5.0.5 media kit

Hello We are running a pretty old system here which needs to be re-installed. Unfortunately even if all my licences are okay, my install CD are missing in the box. I contacted sco in order to get these media kit, with no luck (product discontinued) I was wondering if some good pal would... (5 Replies)
Discussion started by: qube001
5 Replies

3. SCO

OpenServer 5.0.6 Media Needed

I have a client with 5.0.6 who wants to migrate to new hardware. We have in our posession all appropriate paper software licenses. Over the years the media has vanished Can anyone assist with locating an ISO or actual CD containing OpenServer 5.0.6, please? Thank you (9 Replies)
Discussion started by: theantisco
9 Replies

4. SCO

openserver 5.0.6 media need

I am looking for openserver 5.0.6 media. I need build a new production server and we only have the 5.0.5 media. If anybody can help that be awesome. (9 Replies)
Discussion started by: stlwindadmin
9 Replies

5. SCO

SCO Unix OpenServer 5.0.5 Media Kit

My client has lost the SCO OS 5.0.5 install media. However, they do have a working SCO 5.0.5 system, but is crumbling apart. Where can I find the SCO OS 5.0.5 install media? Or can I get a copy of the SCO CD as a ISO file? Your help is much appreciated. (7 Replies)
Discussion started by: chedlee88-1
7 Replies

6. SCO

SCO Openserver 5.0.4Eb binaries needed

Hello, I'm a system administrator of Russian bowling club located in Tomsk. As a server for our management system we use SCO OpenServer 5.0.4Eb. I know that it's old and so on, but we use it because we, some time ago, bought all the bowling system in used condition, and it works well for years. ... (2 Replies)
Discussion started by: mr_Well
2 Replies

7. SCO

SCO 5.0.6 Media needed

Hi, can anyone provide me the sources for sco 5.0.6 as iso? Thanks! (26 Replies)
Discussion started by: VoidCeroOne
26 Replies

8. SCO

Sco media needed for openserver 5.0.6

Hello, i need if possible media for sco openserver 5.0.6 and also want to know if is possible to upgrade from 5.0.2 to 5.0.6. Best regards, Paolo (1 Reply)
Discussion started by: elnino981
1 Replies

9. SCO

Need SCO 5.0.6 openserver media kit

hello everyone i need a copy of sco 5.0.6 iso for isntall a new server crash I read in a post that someone uploaded to an ftp an iso but I did not find the ftp any can helpme? (7 Replies)
Discussion started by: mjgeddo
7 Replies

10. SCO

SCO OpenServer 5.0.6 media needed

My media disk is unusable. Can someone provide me an ISO for Openserver 5.0.6? Thank you. Brantley Allen (2 Replies)
Discussion started by: brantleyallen
2 Replies
OCF_HEARTBEAT_VIRTUA(7) 					OCF resource agents					   OCF_HEARTBEAT_VIRTUA(7)

NAME
ocf_heartbeat_VirtualDomain - Manages virtual domains through the libvirt virtualization framework SYNOPSIS
VirtualDomain [start | stop | status | monitor | migrate_to | migrate_from | meta-data | validate-all] DESCRIPTION
Resource agent for a virtual domain (a.k.a. domU, virtual machine, virtual environment etc., depending on context) managed by libvirtd. SUPPORTED PARAMETERS
config Absolute path to the libvirt configuration file, for this virtual domain. (unique, required, string, no default) hypervisor Hypervisor URI to connect to. See the libvirt documentation for details on supported URI formats. The default is system dependent. (optional, string, no default) force_stop Always forcefully shut down ("destroy") the domain on stop. The default behavior is to resort to a forceful shutdown only after a graceful shutdown attempt has failed. You should only set this to true if your virtual domain (or your virtualization backend) does not support graceful shutdown. (optional, boolean, default 0) migration_transport Transport used to connect to the remote hypervisor while migrating. Please refer to the libvirt documentation for details on transports available. If this parameter is omitted, the resource will use libvirt's default transport to connect to the remote hypervisor. (optional, string, no default) migration_network_suffix Use a dedicated migration network. The migration URI is composed by adding this parameters value to the end of the node name. If the node name happens to be an FQDN (as opposed to an unqualified host name), insert the suffix immediately prior to the first period (.) in the FQDN. At the moment Qemu/KVM and Xen migration via a dedicated network is supported. .sp Note: Be sure this composed host name is locally resolveable and the associated IP is reachable through the favored network. (optional, string, no default) monitor_scripts To additionally monitor services within the virtual domain, add this parameter with a list of scripts to monitor. .sp Note: when monitor scripts are used, the start and migrate_from operations will complete only when all monitor scripts have completed successfully. Be sure to set the timeout of these operations to accommodate this delay. (optional, string, no default) SUPPORTED ACTIONS
This resource agent supports the following actions (operations): start Starts the resource. Suggested minimum timeout: 90. stop Stops the resource. Suggested minimum timeout: 90. status Performs a status check. Suggested minimum timeout: 30. Suggested interval: 10. monitor Performs a detailed status check. Suggested minimum timeout: 30. Suggested interval: 10. migrate_from Executes steps necessary for migrating the resource away from the node. Suggested minimum timeout: 60. migrate_to Executes steps necessary for migrating the resource to the node. Suggested minimum timeout: 120. meta-data Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5. validate-all Performs a validation of the resource configuration. Suggested minimum timeout: 5. EXAMPLE
The following is an example configuration for a VirtualDomain resource using the crm(8) shell: primitive p_VirtualDomain ocf:heartbeat:VirtualDomain params config=string meta allow-migrate="true" op monitor depth="0" timeout="30" interval="10" SEE ALSO
http://www.linux-ha.org/wiki/VirtualDomain_(resource_agent) AUTHOR
Linux-HA contributors (see the resource agent source for information about individual authors) resource-agents UNKNOWN 03/09/2014 OCF_HEARTBEAT_VIRTUA(7)
All times are GMT -4. The time now is 06:26 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy