03-11-2015
the fullcore setting - which is what the syslog/errpt message was about are more specific to application/system 'crashes' that result in a machine-binary core dump.
Java has it's own style of coredumps, text if I recall, and so I suspect they fall under the fsize setting, rather than coresize.
Under normal circumstances you should not be having a lot of coredumps - so setting it unlimited should not be a concern. If you are debugging an issue having an incomplete dump (that is maybe hard to generate) is a tremendous headache - again I would go for unlimited.
When you doubt you will ever use a core for analysis - then you could keep them sized smaller than unlimited.
My opinion, hope it helps.
This User Gave Thanks to MichaelFelt For This Post:
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
As a UNIX newbie, how can I create a (cron)script that rotates my syslogs on AIX 4.3.3 on a 24 hour basis and compresses the old logs ?
TIA ! (1 Reply)
Discussion started by: fireblade
1 Replies
2. Linux
I have the auditd running and I need to send the audit logs to a remote syslog server.
Anyideas on how to do that? (1 Reply)
Discussion started by: jmathenge
1 Replies
3. Solaris
(I will not duplicate my post that I create in 'Programming' ( My post ), but the issue also (after C ) is related to Sun Solaris.)
I need to find the warning-codes to be used in the
#pragma warn..
C-code directives to suppress some compilation warnings.
More desciptive explanation you... (2 Replies)
Discussion started by: alex_5161
2 Replies
4. Programming
I am not able to find warn-codes that should be used in
#pragma warn -<code>
directive!:wall:
Could anybody advise where I can see a list of warnings with codes that (as I understand) should be 3-letters code?
I have a pro-C program that produces some warnings.
(Do not advise,... (4 Replies)
Discussion started by: alex_5161
4 Replies
5. UNIX for Dummies Questions & Answers
hi guys
I have suse 11 sp1 and I have a lot of warn file filling / these are under /var/log
there's this big one
-rw-r----- 1 root root 3.9G Feb 1 10:28 warn
warn: ASCII text
and the others that are about 2.5 to 3MB - they are about 130 warn-*.bz2
-rw-r----- 1 root root 3.9G Feb... (2 Replies)
Discussion started by: karlochacon
2 Replies
6. Solaris
Hi all
I have a newly installed Oracle X2-4 server running Solaris 10 x86 with the latest patches.
I have one non-global zone configured running an Oracle DB instance.
After configuring IPMP failover between two NICs on the server and rebooting I am seeing the /var/adm/messages being flooded... (7 Replies)
Discussion started by: notreallyhere
7 Replies
7. Programming
(Apologies for any typos.)
OSX 10.12.3 AND Windows 10.
This is for the serious Python experts on at least 3.5.x and above...
In script format sys.stdout.write() AND sys.stderr.write() seems to work correctly.
Have I found a serious bug in the interactive sys.stdout.write() AND... (2 Replies)
Discussion started by: wisecracker
2 Replies
8. Red Hat
I'm running CentOS 6.8 and use bash. I would like a warning to appear to the user who runs the command "service httpd restart"
E.g.
# service httpd restart
are you sure y/n
n
#
(or if y, the command executes).
I looked into it a little but am not sure of the best approach. Aliases I ... (1 Reply)
Discussion started by: spacegoose
1 Replies
9. Red Hat
I'm running CentOS 6.8 and use bash. I would like a warning to appear to the user who runs the command "service httpd restart"
E.g.
# service httpd restart
are you sure y/n
n
#
(or if y, the command executes).
I looked into it a little but am not sure of the best approach. Aliases I... (2 Replies)
Discussion started by: spacegoose
2 Replies
10. UNIX for Advanced & Expert Users
When I tried to configure GNU make, I received:...
WARNING: Your system has neither waitpid() nor wait3().
Without one of these, signal handling is unreliable
You should be aware that running GNU make with -j
could result in erratic behavior.
...
What is that supposed to mean ? my spec:
... (1 Reply)
Discussion started by: abdulbadii
1 Replies
KGDB(1) BSD General Commands Manual KGDB(1)
NAME
kgdb -- kernel debugger
SYNOPSIS
kgdb [-a | -f | -fullname] [-b rate] [-q | -quiet] [-v] [-w] [-d crashdir] [-c core | -n dumpnr | -r device] [kernel [core]]
DESCRIPTION
The kgdb utility is a debugger based on gdb(1) that allows debugging of kernel core files.
The options are as follows:
-a Increase the annotation level. An annotation level of 1 features the historical -fullname option of gdb(1). This is useful
when running kgdb in Emacs. The -f or -fullname options are supported for backward compatibility as well.
-b rate Set the baudrate to rate.
-q Suppress printing of the banner when the debugger starts. The -quiet form is supported for compatibility as well.
-v Increase verbosity.
-w Opens kmem-based targets in read-write mode. (This is identical to what --wcore used to do in previous gdb versions for
FreeBSD.)
-d crashdir Use crashdir instead of the default, /var/crash to locate kernel core dump files in. The name vmcore. plus the dump number will
be appended to determine the actual dump file name.
-c core Explicitly use core as the core dump file.
-n dumpnr Use the kernel core dump file numbered dumpnr for debugging.
-r device Use device to connect kgdb to for a remote debugging session.
The -c, -n, and -r options are mutually exclusive.
Optionally, the name of the kernel symbol file and the name of the core dump file can be supplied on the command-line as positional argu-
ments. If no kernel symbol file name has been given, the symbol file of the currently running kernel will be used. If no core dump file has
been specified through either of the options or the last command-line argument, /dev/mem will be opened to allow debugging the currently run-
ning kernel.
FILES
/dev/mem Default memory image to open if no core dump file has been specified.
/var/crash Default directory to locate kernel core dump files.
SEE ALSO
gdb(1)
HISTORY
The kgdb utility first appeared in its current form in FreeBSD 5.3.
BSD
October 11, 2006 BSD