03-11-2015
there are two types of cores in conjunction with Java:
- "normal" AIX cores
- Java cores and heapdumps
fullcore and ulimit regulates "normal" AIX cores, not Java cores. If a java process dumps, it can produce just java dump and no AIX core file. In this case it doesn't matter if fullcore=yes and ulimit -с = unlimited. But it can also be the other case - the process (because it is AIX process) dumps a core and Java has no idea about this dump and doesn't write its own dump. In this case it is better to have fullcore=yes and ulimit -c = unlimited.
But before setting ulimit (or better - chuser core=-1 username ;-) ask your AIX administrator. In many environments it is forbidden to produce full core dumps because of security and because the filesystem can be overflowed with dumps, if you forget to remove them.
This User Gave Thanks to agent.kgb 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
LEARN ABOUT DEBIAN
jifty::logger
Jifty::Logger(3pm) User Contributed Perl Documentation Jifty::Logger(3pm)
NAME
Jifty::Logger -- A master class for Jifty's logging framework
DESCRIPTION
Jifty uses the Log4perl module to log error messages. In Jifty programs there's two ways you can get something logged:
Firstly, Jifty::Logger captures all standard warnings that Perl emits. So in addition to everything output from perl via the warnings
pragmas, you can also log messages like so:
warn("The WHAM is overheating!");
This doesn't give you much control however. The second way allows you to specify the level that you want logging to occur at:
Jifty->log->debug("Checking the WHAM");
Jifty->log->info("Potential WHAM problem detected");
Jifty->log->warn("The WHAM is overheating");
Jifty->log->error("PANIC!");
Jifty->log->fatal("Someone call Eddie Murphy!");
Configuring Log4perl
Unless you specify otherwise in the configuration file, Jifty will supply a default Log4perl configuration.
The default log configuration that logs all messages to the screen (i.e. to STDERR, be that directly to the terminal or to the FastCGI log
file.) It will log all messages of equal or higher priority to the LogLevel configuration option.
---
framework:
LogLevel: DEBUG
You can override the LogLevel configuration option by setting JIFTY_LOG_LEVEL in your environment.
You can tell Jifty to use an entirely different Logging configuration by specifying the filename of a standard Log4perl config file in the
LogConfig config option (see Log::Log4perl for the format of this config file.)
---
framework:
LogConfig: etc/log4perl.conf
Note that specifying your own config file prevents the LogLevel config option from having any effect.
You can tell Log4perl to check that file periodically for changes. This costs you a little in application performance, but allows you to
change the logging level of a running application. You need to set LogReload to the frequency, in seconds, that the file should be
checked.
---
framework:
LogConfig: etc/log4perl.conf
LogReload: 10
(This is implemented with Log4perl's init_and_watch functionality)
METHODS
new COMPONENT
This class method instantiates a new "Jifty::Logger" object. This object deals with logging for the system.
Takes an optional name for this Jifty's logging "component" - See Log::Log4perl for some detail about what that is. It sets up a "warn"
handler which logs warnings to the specified component.
_warning_action
change the Log4Perl action from warn to error|info|etc based on the content of the warning.
Added because DBD::Pg throws up NOTICE and other messages as warns, and we really want those to be info (or error, depending on the code).
List based on Postgres documentation
TODO: needs to be smarter than just string matching
returns a valid Log::Log4Perl action, if nothing matches will return the default of warn since we're in a __WARN__ handler
AUTHOR
Various folks at Best Practical Solutions, LLC.
Mark Fowler <mark@twoshortplanks.com> fiddled a bit.
perl v5.14.2 2011-02-09 Jifty::Logger(3pm)