Sponsored Content
Top Forums UNIX for Dummies Questions & Answers nim mksysb - 0042-124 c_ch_nfsexp error Post 302223785 by astjen on Monday 11th of August 2008 11:08:05 AM
Old 08-11-2008
 

10 More Discussions You Might Find Interesting

1. AIX

NIM mksysb recovery

I have multiple LPARS on p650 with mix of AIX5.2 and AIX5.1 with different rml level My understanding is creating mksysb nim on NIM server is for new installation of LPARS Then; How do I do mksysb backup on existing lpars for recovery purpose or how do I do all mksysb to a NFS mounted Filesystem... (1 Reply)
Discussion started by: melindaj
1 Replies

2. UNIX for Advanced & Expert Users

NIM - mksysb of remote server

Hi, I'm trying to use my NIM server to get a mksysb of an lpar on another machine on my network. I'm trying to define a resource through smitty and i've entered the resource name, Server of resource & location of resource, they are as follows Resource Name : gmt_fail_mksysb Server of... (1 Reply)
Discussion started by: KeesH
1 Replies

3. Shell Programming and Scripting

script to automate mksysb via nim in AIX 5.3

#!/bin/ksh # # nim_mksysb # get mksysb from each client machine specified with -m. If no # machines specified, get mksysb from ALL machines. -r flag says # remove oldest existing mksysb for the machines being backed up. # use -n no_make flag with -r to remove a generation of mksysb, #... (0 Replies)
Discussion started by: barkath
0 Replies

4. AIX

NIM client mksysb restore

Can a NIM client mksysb restore be performed via NIM (smitty nim) without the NIM client machine having the NIM server's IP and hostname in its /etc/hosts file? (10 Replies)
Discussion started by: kah00na
10 Replies

5. AIX

nim mksysb error :/usr/bin/savevg[33]: 1016,07: syntax error

-------------------------------------------------------------------------------- Hello, help me please. I am trying to create a mksysb bakup using nim. I am geting this error, how to correct it ? : Command : failed stdout: yes stderr: no... (9 Replies)
Discussion started by: astjen
9 Replies

6. AIX

nim mksysb buffer overflow error

Hi, I am trying to backup a system ("client") through a slow network using "nim mksysb" on a nim server ("master") The backup starts, but doesn't success. Thanks if you can help me to resolve this problem : Creating information file (/image.data) for rootvg... Creating list of files to... (2 Replies)
Discussion started by: astjen
2 Replies

7. AIX

how to create a package from mksysb via nim ?

Hello, I need to install "bos.adt.libm 5.3.0.0" on a server (AIX5.3 power 5). How to install it from a nim mksysb of an another partition ? Thank you (3 Replies)
Discussion started by: astjen
3 Replies

8. AIX

AIX 5L nim mksysb command

Hi All, Please excuse the possibly naive question but I'm trying to clone/install a new AIX 5.3 LPAR on a p570 from a mksysb image file using nim. Has anyone done this before and if so, what would the exact command look like? Does it even remotely resemble something like nim -o... (1 Reply)
Discussion started by: combustables
1 Replies

9. AIX

mksysb restoration using NIM

Hi, I just want to ask whether anyone has experience on restoring mksysb backup in NIM. We have taken the mksysb backup and the SPOT has been configured on NIM also. I just want to know the checkpoints before doing this. Is there any checkpoints we need to do? Do we need to unmirrorvg? This... (12 Replies)
Discussion started by: depam
12 Replies

10. AIX

mksysb using NIM

I am implementing mksysb backups using NIM. I am using nimsh as client communication and mksysb backup are working fine, but this requires remote logon to be enabled for root. Any thoughts on how can I implement mksysb backups using NIM without enabling remote logon for "root" ? (1 Reply)
Discussion started by: mk8570
1 Replies
Git::Repository::Command(3pm)				User Contributed Perl Documentation			     Git::Repository::Command(3pm)

NAME
Git::Repository::Command - Command objects for running git SYNOPSIS
use Git::Repository::Command; # invoke an external git command, and return an object $cmd = Git::Repository::Command->new(@cmd); # a Git::Repository object can provide more context $cmd = Git::Repository::Command->new( $r, @cmd ); # options can be passed as a hashref $cmd = Git::Repository::Command->new( $r, @cmd, \%option ); # $cmd is basically a hash, with keys / accessors $cmd->stdin(); # filehandle to the process' stdin (write) $cmd->stdout(); # filehandle to the process' stdout (read) $cmd->stderr(); # filehandle to the process' stdout (read) $cmd->pid(); # pid of the child process # done! $cmd->close(); # exit information $cmd->exit(); # exit status $cmd->signal(); # signal $cmd->core(); # core dumped? (boolean) # cut to the chase my ( $pid, $in, $out, $err ) = Git::Repository::Command->spawn(@cmd); DESCRIPTION
"Git::Repository::Command" is a class that actually launches a git commands, allowing to interact with it through its "STDIN", "STDOUT" and "STDERR". This class is a subclass of "System::Command", meant to be invoked through "Git::Repository". METHODS
As a subclass of "System::Command", "Git::Repository::Command" supports the following methods: new( @cmd ) Runs a git command with the parameters in @cmd. If @cmd contains a "Git::Repository" object, it is used to provide context to the git command. If @cmd contains one or more hash reference, they are taken as option hashes. The recognized keys are: "git" The actual git binary to run. By default, it is just "git". In case the "git" to be run is actually a command with parameters (e.g. when using sudo or another command executer), the option value should be an array reference with the command and parameters, like this: { git => [qw( sudo -u nobody git )] } "cwd" The current working directory in which the git command will be run. "env" A hashref containing key / values to add to the git command environment. "input" A string that is send to the git command standard input, which is then closed. Using the empty string as "input" will close the git command standard input without writing to it. Using "undef" as "input" will not do anything. This behaviour provides a way to modify options inherited from "new()" or a hash populated by some other part of the program. On some systems, some git commands may close standard input on startup, which will cause a SIGPIPE when trying to write to it. This will raise an exception. If the "Git::Repository" object has its own option hash, it will be used to provide default values that can be overridden by the actual option hash passed to "new()". If several option hashes are passed to "new()", they will all be merged, keys in later hashes taking precedence over keys in earlier hashes. The "Git::Repository::Command" object returned by "new()" has a number of attributes defined (see below). close() Close all pipes to the child process, and collects exit status, etc. and defines a number of attributes (see below). final_output() Collect all the output, and terminate the command. Returns the output as a string in scalar context, or as a list of lines in list context. Also accepts a hashref of options. Lines are automatically "chomp"ed. If the Git command printed anything on stderr, it will be printed as warnings. If the git sub-process exited with status 128 (fatal error), or 129 (usage message), it will "die()". Accessors The attributes of a "Git::Repository::Command" object are also accessible through a number of accessors. The object returned by "new()" will have the following attributes defined: cmdline() Return the command-line actually executed, as a list of strings. pid() The PID of the underlying git command. stdin() A filehandle opened in write mode to the child process' standard input. stdout() A filehandle opened in read mode to the child process' standard output. stderr() A filehandle opened in read mode to the child process' standard error output. Regarding the handles to the child git process, note that in the following code: my $fh = Git::Repository::Command->new( @cmd )->stdout; $fh is opened and points to the output of the git subcommand, while the anonymous "Git::Repository::Command" object has been destroyed. Once $fh is destroyed, the subprocess will be reaped, thus avoiding zombies. After the call to "close()", the following attributes will be defined: exit() The exit status of the underlying git command. core() A boolean value indicating if the command dumped core. signal() The signal, if any, that killed the command. AUTHOR
Philippe Bruhat (BooK), "<book at cpan.org>" ACKNOWLEDGEMENTS
The core of "Git::Repository::Command" has been moved into its own distribution: "System::Command". Proper Win32 support is now delegated to that module. Before that, the Win32 implementation owed a lot to two people. First, Olivier Raginel (BABAR), who provided me with a test platform with Git and Strawberry Perl installed, which I could use at any time. Many thanks go also to Chris Williams (BINGOS) for pointing me towards perlmonks posts by ikegami that contained crucial elements to a working MSWin32 implementation. COPYRIGHT
Copyright 2010-2011 Philippe Bruhat (BooK), all rights reserved. LICENSE
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. perl v5.14.2 2011-12-28 Git::Repository::Command(3pm)
All times are GMT -4. The time now is 03:03 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy