Sponsored Content
Full Discussion: Ignite
Operating Systems HP-UX Ignite Post 302983417 by gregsih on Tuesday 11th of October 2016 11:18:24 AM
Old 10-11-2016
Ignite

Hi

Does anybody know how to get hold of a very old (A.3.7.n) copy of the ignite software depot for HP-UX 10.20?
 

10 More Discussions You Might Find Interesting

1. HP-UX

ignite tapes

can any1 tell me how to make ignite tapes for the HP-ux. this company said it was: "make_tape_recovery_A", but that don't work. (4 Replies)
Discussion started by: JBX
4 Replies

2. UNIX for Advanced & Expert Users

without an ignite server ??

system: HP-UX 10.20 with HFS mounted. How can I convert the HFS to VxFS without an ignite server ? Is this possible ? thanks simon2000 (4 Replies)
Discussion started by: simon2000
4 Replies

3. HP-UX

make_sys_image + Ignite problem

could any one help me I have a HP UX 11.0 with a lot of VG and disks connected to SAN. I need to create a Golden Image having only the vg00 of this system. How do i do this using make_sys_image? In case any have some docs, I would appreciate if You could share it. Thanks Dhanish (5 Replies)
Discussion started by: i2admin
5 Replies

4. HP-UX

HP-UX Ignite server

Sorry if this has been asked and answered, but I can't find this particual problem. I've had an Ignite server running for years on a small internal network with images we load on daily basis. Tried to load two servers, L2000 and C3600 , both with same problem. # boot lan.192.168.2.2 install ... (0 Replies)
Discussion started by: ddeblance
0 Replies

5. HP-UX

Need Ignite for HP-UX 10.20

Hello All, I need to bring down our old 9000 series d350, but my supervisor wants an ignite backup created. I cannot find ignite in the usual places (/opt/ignite) nor can I find it in swlist. As far as I can tell the cd's are long gone. Is there anywhere else I could look for ignite being... (6 Replies)
Discussion started by: stay0ut
6 Replies

6. HP-UX

vpar ignite

Hi Can I use a vpar as an ignite server? (1 Reply)
Discussion started by: mahlathini
1 Replies

7. AIX

ignite equivalent in AIX

Hi All, Does AIX has utility like ignite server to make remote os installation using image (2 Replies)
Discussion started by: jayannair
2 Replies

8. HP-UX

Ignite and HP-UX 09.XX

I am looking to make bootable tape backups of four machines running HP-UX 09.02, 09.05 and 09.07. I successfully located Ignite 10.20 and installed it and made a backup on the one machine running HP-UX 10.20. I am having trouble locating information about Ignite for HP-UX 9. Does it exist? Is... (3 Replies)
Discussion started by: whack_job
3 Replies

9. HP-UX

Ignite - make_net_recovery

I've read the Ignite User/Admin Guide but I'm having trouble figuring out if I can do a make_net_recovery if the ignite server and client server are on completely different networks? If this can be done is there any special configuration? If I initiate the command from the server it looks like it... (3 Replies)
Discussion started by: gonzotonka
3 Replies

10. HP-UX

Error with ignite

Works all. Depot shared via nfs dhcp working setting file system,network,root password,etc But when i start "go!" with installation,give me this error. How to fix,debug? Thanks http://s24.postimg.org/5hzbgk551/unixbell3.png (3 Replies)
Discussion started by: Linusolaradm1
3 Replies
SVK::XD(3)						User Contributed Perl Documentation						SVK::XD(3)

NAME
SVK::XD - svk depot and checkout handling. SYNOPSIS
use SVK::XD; $xd = SVK::XD->new (depotmap => { '' => '/path/to/repos'}); TERMINOLOGY
depot A repository referred by a name. The default depot is '' (the empty string). depotpath A path referred by a depot name and the path inside the depot. For example, //foo/bar means /foo/bar in the default depot '', and /test/foo/bar means /foo/bar in the depot test. copath Checkout path. A path in the file system that has a checked out version of a certain depotpath. CONSTRUCTOR
Options to "new": depotmap A hash reference for depot name and repository path mapping. checkout A Data::Hierarchy object for checkout paths mapping. giantlock A filename for global locking. This file protects all read and write accesses to the "statefile". When SVK begins to execute any command, it attempt to get a write lock on this "giant lock" file. Once it gets the lock, it writes its PID to the file, reads in its "statefile", and begins to execute the command. Executing the command consists of a "lock" phase and a "run" phase. During the lock phase, a command can do one of three things: request to keep the giant lock for the entire execution (for commands which modify large parts of the "statefile"), request to lock individual checkout paths, or not request a lock. In the first case, the command sets the "hold_giant" field on the SVK::Command object (this should probably change to a real API), and the command does not release the giant lock until it is finished; it can rewrite the "statefile" at the end of its execution without waiting on the lock, since it already holds it. In the second case, the command calls "lock" on the SVK::XD object one or more times; this places a "lock" entry inside the Data::Hierarchy object in the statefile next to each locked path, unless they are already locked by another process. Between its lock phase and its run phase, the "statefile" is written to disk (with the new "lock" entries) and the giant lock is dropped. After the run phase, SVK acquires the giant lock again, reads in the "statefile", copies all entries from the paths that it has locked into the version it just read, clears the lock entries from the hierarchy, writes the "statefile" to disk, and drops the giant lock. Any changes to the hierarchy other than in the locked paths will be ignored. In the third case, SVK just drops the giant lock after the lock phase and never tries to read or write the "statefile" again. statefile Filename for serializing "SVK::XD" object. svkpath Directory name of "giantlock" and "statefile". METHODS
Serialization and locking load Load the serialized "SVK::XD" data from statefile. Initialize $self if there's nothing to load. The giant lock is acquired when calling "load". store store Serialize $self to the statefile. If giant lock is still ours, overwrite the file directly. Otherwise load the file again and merge the paths we locked into the new state file. After "store" is called, giant is unlocked. lock Lock the given checkout path, store the state with the lock info to prevent other instances from modifying locked paths. unlock Unlock all the checkout paths that were locked by this instance. giant_lock Lock the statefile globally. All other instances need to wait for the lock before they can do anything. giant_unlock Release the giant lock. Depot and path translation find_repos Given depotpath and an option about if the repository should be opened. Returns an array of repository path, the path inside repository, and the "SVN::Repos" object if caller wants the repository to be opened. find_repos_from_co Given the checkout path and an option about if the repository should be opened. Returns an array of repository path, the path inside repository, the absolute checkout path, the checkout info, and the "SVN::Repos" object if caller wants the repository to be opened. find_repos_from_co_maybe Like "find_repos_from_co", but falls back to see if the given path is a depotpath. In that case, the checkout paths returned will be undef. find_depotname create_path_object Creates and returns a new path object. It can be either SVK::Path::Checkout, SVK::Path::View or SVK::Path. Takes a hash with arguments. If "copath_anchor" argument is defined then SVK::Path::Checkout is created and other arguments are used to build its "source" in SVK::Path::Checkout using this method. If "revision" argument is not defined then the one checkout path is based on is used. If "view" argument is defined then SVK::Path::View is created and other arguments are used to build its "source" in SVK::Path::Checkout using this method. Otherwise SVK::Path is created. Depot can be passed as SVK::Depot object in "depot" argument or using "depotname", "repospath" and "repos" arguments. Object takes precendence. Checkout handling auto_prop Return a hash of properties that should attach to the file automatically when added. depot_delta Generate "SVN::Delta::Editor" calls to represent the changes between "(oldroot, oldpath)" and "(newroot, newpath)". oldpath is a array ref for anchor and target, newpath is just a string. Options: editor The editor receiving delta calls. no_textdelta Don't generate text deltas in "apply_textdelta" calls. no_recurse notice_ancestry checkout_delta Generate "SVN::Delta::Editor" calls to represent the local changes made to the checked out revision. Options: delete_verbose Generate delete_entry calls for sub-entries within deleted entry. absent_verbose Generate absent_* calls for sub-entries within absent entry. unknown_verbose generate cb_unknown calls for sub-entries within absent entry. absent_ignore Don't generate absent_* calls. expand_copy Mimic the behavior like SVN::Repos::dir_delta, lose copy information and treat all copied descendents as added too. cb_ignored Called for ignored items if defined. cb_unchanged Called for unchanged files if defined. get_entry($copath) Returns the Data::Hierarchy entry and the schedule of the entry. get_fh Returns a file handle with keyword translation and line-ending layers attached. get_props Returns the properties associated with a node. Properties schedule for commit are merged if $copath is given. perl v5.10.0 2008-08-04 SVK::XD(3)
All times are GMT -4. The time now is 02:00 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy