Sponsored Content
Operating Systems AIX 0653-340 There is not enough memory available now Post 302895407 by amp24 on Monday 31st of March 2014 03:56:10 PM
Old 03-31-2014
Hello again vbe,

I had few questions I was hoping you might be able to help me with:

1) Below are the 3 instructions for increasing the data segments.
Code:
export LDR_CNTRL=MAXDATA=0x10000000 start_process unset LDR_CNTRL

Am I correct that the second instructions "start_process" is not a command to run but instead is actually telling you to work on whatever it is you need the size of the data segments increased for?



2) I ran a test and instead of nfs mounting all of /directoryA to the AIX 4.3.3 machine, I just nfs mounted a subdirectory /directoryA/subdirectory1 to the AIX 4.3.3 machine. I was able to go into the mounted subdirectory1 and could successfully run "ls" and "make". This subdirectory only had a few files in it. This makes me again think that the number of files is the cause of the problem. Are there any other values (environmental variables, etc...) that I might be able to change to allow for "ls" and more importantly "make" to successfully run in a directory with many files in it?

Thanks again for your continued assistance

Last edited by zaxxon; 04-01-2014 at 08:20 AM.. Reason: code tags
 

3 More Discussions You Might Find Interesting

1. AIX

0653-421 mksysb errot

When i am taking mksysb that time it is giving error 0653-421 error. (8 Replies)
Discussion started by: pernasivam
8 Replies

2. Shell Programming and Scripting

sort: 0653-657 A write error occurred while sorting.

Hi I am trying to sort a file of 88075743B size. I am doing some processing on the file and after the processing is done; I get 2 files temp1 and temp2. I need to combine both these files as one and this final file should be sorted on fields 1 and 2. Space is the delimiter between fields. Record... (2 Replies)
Discussion started by: diksha2207
2 Replies

3. HP-UX

HP 9000 340 help

Hi all, I've salveaged a fully working HP 9000 340 model with hard disk and floppy drive. It boots up and I get to the login screen. I don't have any usernames or passwords. Anyone know any hacks for the version of Unix it runs? Is there anyway I can reset the root password? Via Floppy? ... (0 Replies)
Discussion started by: robbo007
0 Replies
SYSTEMD-MACHINE-ID-SETUP(1)                                  systemd-machine-id-setup                                  SYSTEMD-MACHINE-ID-SETUP(1)

NAME
systemd-machine-id-setup - Initialize the machine ID in /etc/machine-id SYNOPSIS
systemd-machine-id-setup DESCRIPTION
systemd-machine-id-setup may be used by system installer tools to initialize the machine ID stored in /etc/machine-id at install time, with a provisioned or randomly generated ID. See machine-id(5) for more information about this file. If the tool is invoked without the --commit switch, /etc/machine-id is initialized with a valid, new machined ID if it is missing or empty. The new machine ID will be acquired in the following fashion: 1. If a valid D-Bus machine ID is already configured for the system, the D-Bus machine ID is copied and used to initialize the machine ID in /etc/machine-id. 2. If run inside a KVM virtual machine and a UUID is configured (via the -uuid option), this UUID is used to initialize the machine ID. The caller must ensure that the UUID passed is sufficiently unique and is different for every booted instance of the VM. 3. Similarly, if run inside a Linux container environment and a UUID is configured for the container, this is used to initialize the machine ID. For details, see the documentation of the Container Interface[1]. 4. Otherwise, a new ID is randomly generated. The --commit switch may be used to commit a transient machined ID to disk, making it persistent. For details, see below. Use systemd-firstboot(1) to initialize the machine ID on mounted (but not booted) system images. OPTIONS
The following options are understood: --root=root Takes a directory path as argument. All paths operated will be prefixed with the given alternate root path, including the path for /etc/machine-id itself. --commit Commit a transient machine ID to disk. This command may be used to convert a transient machine ID into a persistent one. A transient machine ID file is one that was bind mounted from a memory file system (usually "tmpfs") to /etc/machine-id during the early phase of the boot process. This may happen because /etc is initially read-only and was missing a valid machine ID file at that point. This command will execute no operation if /etc/machine-id is not mounted from a memory file system, or if /etc is read-only. The command will write the current transient machine ID to disk and unmount the /etc/machine-id mount point in a race-free manner to ensure that this file is always valid and accessible for other processes. This command is primarily used by the systemd-machine-id-commit.service(8) early boot service. --print Print the machine ID generated or committed after the operation is complete. -h, --help Print a short help text and exit. --version Print a short version string and exit. EXIT STATUS
On success, 0 is returned, a non-zero failure code otherwise. SEE ALSO
systemd(1), machine-id(5), systemd-machine-id-commit.service(8), dbus-uuidgen(1), systemd-firstboot(1) NOTES
1. Container Interface https://www.freedesktop.org/wiki/Software/systemd/ContainerInterface systemd 237 SYSTEMD-MACHINE-ID-SETUP(1)
All times are GMT -4. The time now is 06:34 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy