10-15-2009
have you checked for other limits in the pam configs?
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Does anyone know how to read core dumps. Is gdb the only tool for it ? The OS is Solaris.
Thanks (2 Replies)
Discussion started by: suntan
2 Replies
2. Solaris
I have the following set up on a Sun server running solaris 5.8 for core dump generation
coreadm
global core file pattern: /var/core
init core file pattern: /var/core
global core dumps: enabled
per-process core dumps: enabled
global setid core dumps:... (4 Replies)
Discussion started by: handak9
4 Replies
3. Programming
hi everyone,
Right now when I do:
strcmp(s1, s2);
i get a core dump because at times s1 or s2 can be nothing so that makes strcmp() core dump.
What is the solution, if at times I expect one of them (or both) to be NULL?
I want to be able to compare that s1 is NULL and s2 is "blah" or... (6 Replies)
Discussion started by: annie
6 Replies
4. SCO
Anyone know how you go about interrogating a panic / core dump with crash for SCO Unix (5 Replies)
Discussion started by: ccarcher
5 Replies
5. UNIX for Advanced & Expert Users
Hi,
Can we modify the GDB source code so as to analyze core dumps from different targets? From my analysis, I think we need to build our section table statically for each target. i.e., including the various address boundaries in build_section_table() function. If this is the case, then the GDB... (2 Replies)
Discussion started by: nsdeeps
2 Replies
6. Programming
My program is not dumping core when hitting a segmentation violation inside a thread.
However, it dumps core when the segv occurs within main.
Any ideas on how to diagnose this?
AIX 5.3 (4 Replies)
Discussion started by: bean66
4 Replies
7. Solaris
i had a situation where a process was defunct. preap would not reap the process and gcore would not work properly (not sure why). therefore, the suggestion was to force a panic and collect the core dump. obviously you could do a savecore -L and capture the dump without bringing down the system.... (3 Replies)
Discussion started by: pupp
3 Replies
8. Red Hat
Hi
I have a Fedora installed and I try to generate my application's core dump file.
My system has no coredump limit:
$ ulimit
core file size (blocks, -c) unlimited
But when my application crashes no core dumps generated. I can generate dump file using gcore but it is not appropraite... (1 Reply)
Discussion started by: xyzt
1 Replies
9. Programming
I'm working on a program in Linux with a group of people scattered around the country. When we have a crash, I like to send a core dump to the appropriate person so that they can understand the problem better. The problem is that our application uses several gigabytes worth of data and these... (4 Replies)
Discussion started by: bmsterner
4 Replies
10. HP-UX
kill -SEGV <pid> gives me the core file for that process but also terminates the process.
Can I not get the core dump without terminating the process ? (2 Replies)
Discussion started by: mohtashims
2 Replies
LEARN ABOUT OSF1
rpc.statd
rpc.statd(8) System Manager's Manual rpc.statd(8)
NAME
rpc.statd, statd - Network status monitor daemon
SYNOPSIS
/usr/sbin/rpc.statd [-c]
OPTIONS
Available only on TruCluster Server systems. This option starts the clusterwide network status daemon, which helps provide highly available
NFS service. Do not use -c directly. Highly available NFS service is configured by default and typically does not require intervention. If
you do need to start the clusterwide network status daemon, use the CAA command, caa_start cluster_lockd.
For more information, see the TruCluster Server Administration manual.
DESCRIPTION
The rpc.statd daemon monitors the status of the client and server sites in response to a request made by the local rpc.lockd daemon. When
a site failure is detected, the rpc.statd daemon notifies the local rpc.lockd daemon, which then processes the recovery of the locked files
or file regions.
RESTRICTIONS
The crash of a site is only detected on its recovery.
FILES
A directory created by the statd daemon. Each file name in the directory is the host name of a client or server that the statd daemon will
notify upon its recovery. A backup directory created by the statd daemon. A file created by the statd daemon to store its state number.
SEE ALSO
Daemons: rpc.lockd(8)
Files: statmon(4)
rpc.statd(8)