Sponsored Content
Operating Systems AIX Migration from OLD server to NEW one Post 302095672 by johnf on Thursday 9th of November 2006 04:25:07 AM
Old 11-09-2006
Quite correct we have to wait for an answer. He might want to move from an old 43P to a P510 for all we know. Also storage is storage whether external or internal so he needs to clarify both points! As I said in my first post from what to what?
 

9 More Discussions You Might Find Interesting

1. AIX

How will do migration through NIM server in AIX

Can any one help..... How will do migration through NIM server? (4 Replies)
Discussion started by: AIXlearner
4 Replies

2. Solaris

Server Migration

Hi All We are having a very old server that is working on solaris 5.6 and oracle7. now We are planning to migrate it to a Solaris 8 and oracle 9 environment. The application software of the server is basically written in ProC and there are few sql ,perl and shell scripts on the server . We... (13 Replies)
Discussion started by: asalman.qazi
13 Replies

3. Shell Programming and Scripting

Server Migration: Problems with attributes

I am migrating from a host to another and I am trying to mimic the attributes on the old server. Only problem is I can't figure out a fast way. Any recommendations? Initially I thought about listing all my files on my previous host, but for some reason the listing of all files produced... (2 Replies)
Discussion started by: raykon
2 Replies

4. Linux

CentOS Live Server Migration?

Hello, everyone. I've been lurking on this forum for a while but have never needed to post asking for a bit of help until now. Long story short, I have a test of sorts scheduled with a prospective employer, a managed web hosting company, that involves migrating a hypothetical customer from... (2 Replies)
Discussion started by: Deputy Cartman
2 Replies

5. Solaris

Storage Migration on Solaris server

Hi All, I need your help urgently. Below I have given the brief description of the Architecture and the Problem. The brief details of the architecture: We have 5 Containers(Non-Global Zones) running on one T5220 Box. The Global Zone is running Solaris 10. The Non-global Zones are... (6 Replies)
Discussion started by: kamaldeep1986
6 Replies

6. Red Hat

Print server Migration from AIX to Linux

Hi, Can anyone help me on migration the print server from AIX to RHEL 4? Appreciate your help? (1 Reply)
Discussion started by: brby07
1 Replies

7. UNIX and Linux Applications

Server migration from samba+ldap to windows server 2003

Hi, i have a server installed samba+openldap (pdc). Need to migration windows server 2003 (active directory) object users, computers. Where you can read how to do it? Or can tell me how to do it? Thanks. P.S. Sorry for bad english (0 Replies)
Discussion started by: ap0st0l
0 Replies

8. AIX

Server migration

Hi, Existing several p5 server with lpar (aix5.3), also implemented with hacmp. And now planning to buy new set of server (installing aix7.1)and SAN to replace the existing server. My question is, how to perform data migration from old server/SAN to new server/SAN. Suppose I install... (6 Replies)
Discussion started by: Oceanlo2013
6 Replies

9. Solaris

Server migration - using ufsdump

hi all, i am refreshing my hardware, but i do not want to do a clean installation/reinstallation. I am wondering if i could do - do a ufsdump of the / partition (into a file on a nfs share) - bootup using cdrom in the new machine - mount the boot device/slice, and restore the ufsdump on... (7 Replies)
Discussion started by: javanoob
7 Replies
CAP_COPY_EXT(3) 					     Linux Programmer's Manual						   CAP_COPY_EXT(3)

NAME
cap_copy_ext, cap_size, cap_copy_int - capability state external representation translation SYNOPSIS
#include <sys/capability.h> ssize_t cap_size(cap_t cap_p); ssize_t cap_copy_ext(void *ext_p, cap_t cap_p, ssize_t size); cap_t cap_copy_int(const void *ext_p); USAGE
cc ... -lcap DESCRIPTION
These functions translate a capability state from an internal representation into an external one. The external representation is an exportable, contiguous, persistent representation of a capability state in user-managed space. The internal representation is managed by the capability functions in working storage. cap_size returns the total length (in bytes) that the capability state in working storage identified by cap_p would require when converted by cap_copy_ext. This function is used primarily to determine the amount of buffer space that must be provided to the cap_copy_ext func- tion in order to hold the capability data record created from cap_p. cap_copy_ext copies a capability state in working storage, identified by cap_p, from system managed space to user-managed space (pointed to by ext_p) and returns the length of the resulting data record. The size parameter represents the maximum size, in bytes, of the resulting data record. The cap_copy_ext function will do any conversions necessary to convert the capability state from the undefined internal for- mat to an exportable, contiguous, persistent data record. It is the responsibility of the user to allocate a buffer large enough to hold the copied data. The buffer length required to hold the copied data may be obtained by a call to the cap_size function. cap_copy_int copies a capability state from a capability data record in user-managed space to a new capability state in working storage, allocating any memory necessary, and returning a pointer to the newly created capability state. The function initializes the capability state and then copies the capability state from the record painted to by ext_p into the capability state, converting, if necessary, the data from a contiguous, persistent format to an undefined, internal format. Once copied into internal format, the object can be manipu- lated by the capability state manipulation functions. Note that the record pointed to by ext_p must have been obtained from a previous, successful call to cap_copy_ext for this function to work successfully. The caller should free any releasable memory, when the capability state in working storage is no longer required, by calling cap_free with the cap_t as an argument. RETURN VALUE
cap_size returns the length required to hold a capability data record on success, and -1 on failure. cap_copy_ext returns the number of bytes placed in the user managed space pointed to by ext_p on success, and -1 on failure. cap_copy_int returns a pointer to the newly created capability state in working storage on success, and NULL on failure. On failure, errno(3) is set to EINVAL, ENOMEM, or ERANGE. CONFORMING TO
These functions are specified by POSIX.1e. SEE ALSO
cap_clear(3), cap_from_text(3), cap_get_file(3), cap_get_proc(3), cap_init(3) 26th May 1997 CAP_COPY_EXT(3)
All times are GMT -4. The time now is 07:32 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy