Sponsored Content
Operating Systems AIX IBM TDS/SDS (LDAP) - can I mix endianness among servers in an instance ? Post 303039580 by zxmaus on Wednesday 9th of October 2019 11:35:58 PM
Old 10-10-2019
well endianness only matters for binary data not text data. If I understand you correctly you want to transfer text data only so that should work fine. If you however need something runnable you would need to run it through a converter and recompile.
This User Gave Thanks to zxmaus For This Post:
 

5 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

HP-UX 10.2 servers interoperability with IBM mass storage devices

Does anyone have succesfully interconnected HP-UX 10.2 HP 9000 K370 servers with A6885A HBA's, with an IBM Fastt storage server? I need to replace integrate both platforms. Interoperability matrices from manufacturers do not certified such integration. Thanks for anybody's help. (0 Replies)
Discussion started by: raltmannr
0 Replies

2. UNIX for Dummies Questions & Answers

Is no LDAP unusual for 40+ solaris servers?

I am the new jr admin on a solaris team (2 people). We have over 40 solaris servers (v8 and v9) yet no LDAP to manage it all. Is this unusual? So, if we need to add a new user, we have to add him 40x. Thanks in advance ~R (1 Reply)
Discussion started by: abstractrick
1 Replies

3. AIX

IBM Servers Documentation

Hello dear friends, I wanrt to document our servers configuration but have no Idea which softweare should I use for documenting server environment.. maybe anyone can suggest me which software should I use.. thanks in Advance (2 Replies)
Discussion started by: Vit0_Corleone
2 Replies

4. AIX

executable problems with shell script in IBM servers

We have a java stand alone application running currently on sun Solaris system. The java application runs on Jdk 1.4. We are reshooting this java application to new Ibm servers. There are 10 unix scripts for this application. All scripts works well except one shell script, This shell... (2 Replies)
Discussion started by: poojagupta
2 Replies

5. AIX

Mix LDAP and LOCAL user on AIX

Hello, I'm currently trying to mix local and LDAP users on an AIX 7.1. I've triied many things. My LDAP Server in on a CentOS - OpenLDAP (which works fine with linux). I'm currently stuck on AIX at how to declare LDAP AND Local users. Here's what i did : /usr/sbin/mksecldap -c -h 'ldap03'... (15 Replies)
Discussion started by: AIX_user_324891
15 Replies
plock(2)							System Calls Manual							  plock(2)

NAME
plock() - lock process, text, data, stack, or shared library in memory SYNOPSIS
DESCRIPTION
The system call allows the calling process to lock the text segment of the process (text lock), its data segment (data lock), or both its text and data segment (process lock) into memory. Stack segments are also locked when data segments are locked. Shared library text and shared library data segments (shlib lock) can also be locked. Locked segments are immune to all routine swapping. also allows these seg- ments to be unlocked. The effective user ID of the calling process must be a user with the privilege. op must be one of the following: Lock text and data segments into memory (process lock) Lock text segment into memory (text lock) Lock data segment into memory (data lock) Remove locks Lock shared library text and shared library data segments (shared library lock) Lock text, data and shared library text and shared library data segments into memory (process and shared library lock) Lock text, shared library text and shared library data segments into memory (text and shared library lock) Lock data, shared library text and shared library data segments into memory (data and shared library lock) Although and the family of functions may be used together in an application, each may affect the other in unexpected ways. This practice is not recommended. Security Restrictions Some or all of the actions associated with this system call require the privilege. Processes owned by the superuser have this privilege. Processes owned by other users may have this privilege, depending on system configuration. See privileges(5) for more information about privileged access on systems that support fine-grained privileges. RETURN VALUE
returns the following values: Successful completion. Failure. The requested operation is not performed. is set to indicate the error. ERRORS
If fails, is set to one of the following values. op is equal to and a process lock, a text lock, or a data lock already exists on the calling process. op is equal to and a text lock or process lock already exists on the calling process. op is equal to and a data lock, or process lock already exists on the calling process. op is equal to and no type of lock exists on the calling process. op is equal to and there are no unlocked shared library segments in the calling process. op is equal to and a process lock, a text lock, or a data lock already exists on the calling process. op is equal to and a text lock or process lock already exists on the calling process. op is equal to and a data lock, or process lock already exists on the calling process. op is not equal to one of the values specified in is not allowed in a window. See vfork(2). There is not enough lockable memory in the system to satisfy the locking request. The effective user ID of the calling process is not a user with the privilege. EXAMPLES
The following call to locks the calling process in memory: SEE ALSO
setprivgrp(1M), exec(2), exit(2), fork(2), getprivgrp(2), mlock(2), vfork(2), privileges(5). STANDARDS CONFORMANCE
plock(2)
All times are GMT -4. The time now is 02:27 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy