each time I try to do a bosboot or a mksysb the cpu says that he doesn't find /unix... I don't understand cause the kernel is here on the computer and at this exact place with the right name. I tried to force with -k /unix but it doesn't do anything. He doesn't find it and it is here...
Do you... (6 Replies)
My mksysb scripts gives the following text on standard error:
bosboot: Boot image is 22995 512 byte blocks.
How come on a Aix 5200-07 aix-system.
I thought this message meant that the tape (/dev/rmt0) is not bootable,
but I read about a limit of 12 MB and 22995 block is less than 12 MB
... (0 Replies)
Hi, I'm a noob with AIX, can anybody help me solve this issue I'm stuck with on an 5.3 box.
bash# installp -C
0503-409 installp: bosboot verification starting...
0503-497 installp: An error occurred during bosboot verification processing.
Thanks. (4 Replies)
hi all
i just found one of my p650 server showing a warning message when i
tried to run bosboot command after upgrading TL to AIX 530803.
i also tried to run chpv -c hdisk0 and chpv -c hdisk1 to clear out the
old boot info in hdisk0 and hdisk1 and rerun bosboot -a. it still
showed... (0 Replies)
bosboot -ad hdisk0 give the following error ..
malloc failed
0301-177 A previous bosdebug command has changed characteristics of this
boot image. Use bosdebug -L to display what these changes are.
0301-106 /usr/lib/boot/bin/mkboot_chrp: The malloc call failed for size: 216174592
... (1 Reply)
1) when user login to the server the session got colosed. How will resolve?
2) While firing the command ls -l we are not able to see the any files in the director. but over all view the file system using the command df -g it is showing 91% used. what will be the problem?
Thanks in advance. (1 Reply)
Hi Guys,
I have a problem while trying to upgrade to more current EMC powerpath software on AIX 5.3 - respectively uninstalling the existing one.
I tried to deinstall the powerpath software with removed disks - was working perfectly fine on 12 servers - but number 13 is failing with errors:
... (4 Replies)
Hi,
This is rather a question from a "user" than from a sys admin, but I think this forum is apropriate for the question.
I have an adress with automatic email forwarding and for some senders (two hietherto), emails are bouncing. This has really created a lot of problems those two time so I... (0 Replies)
Hi i wanted to know for what reasons, bosboot fails with the error below.?
# /usr/sbin/bosboot.dp -a -p /usr/lib/boot/chrp.disk.proto -d /dev/ipldevice
dd: 0511-053 The write failed.
: There is a request to a device or address that does not exist.
65893+1 records in.
1029+1 records out.
... (1 Reply)
I don't know if you guys get this problem sometimes at Terminal but I had been having this problem since yesterday :( Maybe I overdid the Terminal. Even the codes that used to work doesn't work anymore.
Here is what 's happening:
* I wanted to remove lines containing digits so I used this... (25 Replies)
Discussion started by: Nexeu
25 Replies
LEARN ABOUT HPUX
dlclose
dlclose(3C)dlclose(3C)NAME
dlclose() - close a shared library
SYNOPSIS
[flag ... ] file ... [library]...
Multithread Usage
This routine is thread-safe.
NOTE: The dynamic loader serializes the loading and unloading of shared libraries in multithreaded applications using a recursive pthread
mutex lock. See the for more information.
DESCRIPTION
is one of a family of routines that give the user direct access to the dynamic linking facilities (using the option on the compiler or com-
mand line). disassociates a shared object previously opened by from the current process. Once an object has been closed using its symbols
are no longer available to All objects loaded automatically as a result of invoking on the referenced object (see dlopen(3C)) are also
closed. handle is the value returned by a previous invocation of
RETURN VALUE
If the referenced object was successfully closed, returns If the object could not be closed, or if handle does not refer to an open object,
returns a non-0 value. More detailed diagnostic information is available through
ERRORS
If fails, a subsequent call to returns one of the following values.
Cannot apply relocation in library.
Cannot close library due to remaining dependencies.
Invalid handle.
Out of memory.
failed on entry to or exit from
failed on exit from
failed on entry to
Unknown handle.
WARNINGS
A successful invocation of does not guarantee that the objects associated with handle have actually been removed from the address space of
the process. Objects loaded by one invocation of may also be loaded by another invocation of The same object may also be opened multiple
times. An object is not removed from the address space until all references to that object through an explicit invocation have been closed
and all other objects implicitly referencing that object have also been closed.
Once an object has been closed by referencing symbols contained in that object can cause undefined behavior.
SEE ALSO dlerrno(3C), dlerror(3C), dlopen(3C), dlsym(3C).
Texts and Tutorials
(See the option)
(See manuals(5) for ordering information)
dlclose(3C)