04-12-2006
Check out:
1. are the runtime (shared libraries) exactly the same release levels for all the software?
2. what patches have been applied to one machine but not to another?
If 1 checks out and there are no differences in patches, then I'd call IBM as well.
It is probably a hardware problem.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
help, what is the difference between core dump and panic dump? (1 Reply)
Discussion started by: aileen
1 Replies
2. UNIX for Dummies Questions & Answers
I've got a core dump in my weblogic home directory, which i have tried to debug by initiating savecore from /etc/init.d/savecore start
but savecore failed to create the two files, that is vmcore.n and vmunix.n.
savecore is enable on my server to save vmcore and vmunix in /var/crash/hostname
1)... (4 Replies)
Discussion started by: hassan2
4 Replies
3. Programming
MY friends:
my program under sco unix have a problem?
it create a core dump file on the path when execute program ,
but i can't find the error of the C program ,i don't know how to
see the error about my program use core, please help me
or give me some suggest and what tools can use... (1 Reply)
Discussion started by: zhaohaizhou
1 Replies
4. AIX
Hi,
We have one application (c language) installed on our AIX 5.2. When we enter some large amount of data in one screen and do update, it is dumping core some times without any error (like bus error, segmentation fault). Next we open the application again and enter the same data and do update.... (0 Replies)
Discussion started by: venkatmyname
0 Replies
5. UNIX for Advanced & Expert Users
Hi All,
i am new to this forum.i want detail of reading the core file and trace the problem because of what the program get crashed.please help me.if any body knows any website or tutoril plese let me know.
sudhir (6 Replies)
Discussion started by: sudhir patnaik
6 Replies
6. UNIX for Dummies Questions & Answers
Hi All
I am new for this forum. I have a core file by using gdb and bt cmd I got the function name but I want to the exact cause of the core dump because of I can not reproduse the binary so if any one know the cmd plz plz plz let me know. (0 Replies)
Discussion started by: gyanusoni
0 Replies
7. SCO
Hello Unix World,
I've been having this issue for the longest time.
Here is my setup
OS: SCO OpenServer 6.0 with mp4, mp3
Server: Dell PowerEdge 840, 800, 2900
USB Stick: Patriot 16GB High Speed, and many other different brands.
Occasinaly while system is running and USB is pluged in the... (0 Replies)
Discussion started by: miles556
0 Replies
8. UNIX for Dummies Questions & Answers
my progrme complaints 'Segmentation fault'.
How to let it print 'Segmentation fault(core dumped)' and generate core dump file?
$ulimit
unlimited (22 Replies)
Discussion started by: vistastar
22 Replies
9. HP-UX
Hi Guys,
I was wondering if somebody could give me a link to a very good source of information or document about core dump process and How to's about it. I have also googled it and found some articles myself.
Thanks
Messi (1 Reply)
Discussion started by: messi777
1 Replies
10. Solaris
Hi guys,
just want to know which core file pattern is best to set for core dumps:
1) per-process file name pattern
or
2) global file name pattern.
I will really appreciate an explanation why the chosen one is better.
Thanks a lot guys. (2 Replies)
Discussion started by: cjashu
2 Replies
cleanup(1M) cleanup(1M)
NAME
cleanup - HP-UX patch cleanup utility
SYNOPSIS
DESCRIPTION
The command provides functions useful when dealing with HP-UX patches on HP-UX.
The command logs all information to
Options
recognizes the following options:
Preview the task but do not actually perform the requested action.
Notify the user of
tasks and request confirmation before performing the requested action.
Commit patches superseded at least
number times. This option is a front-end to the option of (see swmodify(1M)) that provides an easier interface to commit
multiple patches at once.
Remove patches in the specified software depot that have been superseded by
patches also available from the depot.
Specifies whether the software depot contains patches for HP-UX 10.X or 11.X
releases. This option is only valid with the option. If the option is not specified, it defaults to HP-UX 11.X patches.
Specifies whether patches in the software depot that contain a corequisite or
prerequisite attribute specifying one of the superseded patches as a dependency should also be removed. This option is valid
only with the option. If the option is not specified, it defaults to true.
Remove HP-UX 10.X patches that remain in the Installed Product Database
after an upgrade to HP-UX 11.X. These patches are removed from the IPD so that they are no longer displayed in the output of
the command (see swlist(1M)). The HP-UX 10.X patch files are also removed from
Correct the
attribute for HP-UX 11.X patches.
Recommendations
The command should be executed after updating to HP-UX 11.X from HP-UX 10.20. It is not necessary to execute after updating from one ver-
sion of HP-UX 11.X software to another because SD-UX will properly remove 11.X patch information from the IPD in these situations.
The command should be executed whenever patches are added to a software depot. It is not a requirement that superseded 11.X patches be
removed from a software depot, but it is a recommendation to conserve disk space and to avoid confusion. If superseded patches exist in
the same depot as patches that supersede them, SD-UX on HP-UX 11.X will handle the situation properly.
The command can be executed to commit all patches that have been superseded at least the specified number of times. The only benefit from
committing patches is that disk space will be recovered in the
The command can be executed to insure that the attribute of all patch filesets is set correctly. There are several known situations where
the attribute will be set incorrectly. This command can be run at any time, but will be most useful after a system has been installed
using Ignite-UX.
AVAILABILITY
This command is standard on HP-UX 11i v3. On 11i v2 it is available in patch PHCO_32220 or a superseding patch. On 11i v1 it is available
in patch PHCO_27780 or a superseding patch.
WARNINGS
Extreme care should be used when committing patches. Once a patch has been committed, it cannot be removed from the system. Patches
should only be committed when you are satisfied with their behavior. Recovering disk space should not be the only factor considered when
committing patches.
AUTHOR
was developed by HP.
SEE ALSO
show_patches(1), sysdiff(1), check_patches(1M), swlist(1M), swmodify(1M), swremove(1M), sd(4).
cleanup(1M)