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
ppud(1M) ppud(1M)
NAME
ppud - Pay per use daemon
SYNOPSIS
DESCRIPTION
is a daemon that provides system configuration and core usage information to a utility meter system for billing purposes. This daemon runs
on Pay per use systems and meters core utilization and system configuration information. The daemon sends this information to a utility
meter as an XML file.
When a report is sent to a utility meter, it is also written to the file /var/ppu/PPUReport.xml. This report is best viewed using a web
browser that understands XML. If the connection to the utility meter fails, the daemon caches the report data until the connection is
restored.
The daemon re-spawns itself if killed. The following entry is added to /etc/inittab in order to have start and re-spawn itself:
The daemon is automatically started when a system boots if a utility meter has been specified via the command (see ppuconfig(1M)). The
daemon does not need to be restarted when the meter configuration is changed via the command.
The daemon reports errors via syslog.
To unconfigure Pay per use, execute:
Warning: if this is a Pay per use system and the daemon is not running, usage reports will not be sent to HP and usage may be assumed to be
100%.
The daemon performs periodic operations based on the time of day. The daemon is spawned by and gets its timezone specification from the
/etc/default/tz file. By default the timezone specified in /etc/default/tz is EST5EDT. You can specify which timezone the daemon uses to
interpret its current time by modifying the /etc/default/tz file. Refer to environ(5)) for details of the format. A restart of the daemon
is required before the new timezone value takes effect (i.e. kill the /usr/lbin/ppud process).
For more information see the Pay per use User's Guide located at /usr/share/doc/PayPerUseUserGuide.pdf
AUTHORS
ppud was developed by HP.
FILES
/etc/default/tz
File contains the timezone value used by . The format for the file is the same as the the environment variable format without
the prefix . (See environ(5) for details of the TZ format).
/var/ppu/cache/
Directory contains the report data that is cached if the connection to the utility meter fails.
SEE ALSO
ppuconfig(1M), ppu(5)
ppud(1M)