I am generating the coredump of my JBoss, and by default it puts it in to a particular directory. i.e. JBOSS_HOME/. I would like this output file to be created, lets say in /tmp/dump/.
I tried the following:
But it created /tmp/dump/out.txt with 0 KB, and yet it created the dump file in JBOSS_HOME/ directory.
Can you please let me know how can I have kill -3 to create the core dump file in the desired location?
Hi there, i wonder if anyone can help
is there any way that i can write a script that will kill all current ftp processes, for example if ps -ef | grep ftp produces 3 active proceses, then I would like to somehow extract the PID for each one and pass that to kill -9
has anybody done this... (2 Replies)
Hi All,
In my project i have two process runs in the back end.
Once i start my project, and execute the command ps, i get below output:
PID TTY TIME CMD
9086 pts/1 0:00 ksh
9241 pts/1 0:02 java
9240 pts/1 0:00 shell_script_bg
java with 9241 PID is the main... (4 Replies)
Hellow Experts
i have one problem.
i run one script in backgroun.
and i want to kill that script with only script name.....
so what's the solution..
for your info
my script name is "testscript" n it contains "sleep 100"
thanks.... (16 Replies)
Hi,
On my Linux machine, using Bash, I sometimes run into a situation where doing the following does not seem to work at all.
kermit@fastbox ~ $ ps -A | grep firefox-bin
5375 ? 00:06:57 firefox-bin <defunct>
5624 ? 00:00:00 firefox-bin
kermit@fastbox ~ $ kill 5624... (7 Replies)
Hi to everybody.
Is it possible to nohup a process and redirect the output to a file containing the PID?
E.g. if
nohup filename > out.nohup
associate the PID=8074 to filename, is it possible to call the output file something like out_8074.nohup instead of out.nohup? By this way it would... (0 Replies)
Hello,
I have problem with killing red5 process running on linux server. As this process is continuously changing its PID so it can't be killed with "kill -9 PID" command.
First I used following command to list RED5 process
ps aux | grep red5
which showed me
root 5832 0.0 0.0 4820 756pts/0... (1 Reply)
Hi,
I wrote a script to kill a process id.
I am able to kill the PID only if I enter the root password in the middle of the execution because I did not run as root i.e after i run the script from the terminal, instead of killing directly, it is killing only after entering the pass when it... (12 Replies)
Hello Friends,
I've been trying to write a one line which checks java processes and filter them for a user (testuser) and then check process arguments with PARGS command and then check if there is certain patterns exists in pargs output then kill the process.
I have tried the following so... (2 Replies)
I created a program to kill long running pid processes.
I am getting the following error message:
-f command cannot be found.
I also want to count the number of pids that are killed and append the results to a text file. I am new to shell script programming.
1.The first part of code... (10 Replies)
Hi All, Looking for a quick LINUX shell script which can continuously monitors the flle size, report the process which is creating a file greater than certain limit and also kill that process. Can someone please help me on this? (4 Replies)
Discussion started by: vasavimacherla
4 Replies
LEARN ABOUT CENTOS
systemd-coredumpctl
SYSTEMD-COREDUMPCTL(1) systemd-coredumpctl SYSTEMD-COREDUMPCTL(1)NAME
systemd-coredumpctl - Retrieve coredumps from the journal
SYNOPSIS
systemd-coredumpctl [OPTIONS...] {COMMAND} [PID|COMM|EXE|MATCH...]
DESCRIPTION
systemd-coredumpctl may be used to retrieve coredumps from systemd-journald(8).
OPTIONS
The following options are understood:
-h, --help
Print a short help text and exit.
--version
Print a short version string and exit.
-F, --field=
Print all possible data values the specified field takes in matching coredump entries of the journal.
-o, --output=FILE
Write the core to FILE.
--no-pager
Do not pipe output of list into a pager.
--no-legend
Do not print the column headers.
The following commands are understood:
list
List coredumps captured in the journal matching specified characteristics.
dump
Extract the last coredump matching specified characteristics. Coredump will be written on stdout, unless an output file is specified
with -o/--output.
gdb
Invoke the GNU debugger on the last coredump matching specified characteristics.
MATCHING
Match can be:
PID
Process ID of the process that dumped core. An integer.
COMM
Name of the executable (matches COREDUMP_COMM=). Must not contain slashes.
EXE
Path to the executable (matches COREDUMP_EXE=). Must contain at least one slash.
MATCH
General journalctl predicates (see journalctl(1)). Must contain an equals sign.
EXIT STATUS
On success, 0 is returned, a non-zero failure code otherwise. Not finding any matching coredumps is treated as failure.
SEE ALSO systemd-journald.service(8), gdb(1)systemd 208SYSTEMD-COREDUMPCTL(1)