Detaching from program: /sbin/init, process 1
[root@xxx:~]# ps -ef | grep dsmc
root 10765 1 0 Apr19 ? 00:00:00 dsmc q systeminfo policy -console
root 14196 1 0 Apr23 ? 00:00:03 /usr/bin/dsmc schedule -optfile=/opt/tivoli/tsm/client/ba/bin/dsm.opt
root 27110 2182 0 18:41 pts/0 00:00:00 grep dsmc
[root@xxx:~]# gdb
GNU gdb (GDB) Red Hat Enterprise Linux (7.2-83.el6)
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
(gdb) attach 10765
Attaching to process 10765
ptrace: Operation not permitted.
(gdb)
Hi Friends,
Can any of you explain me about the below line of code?
mn_code=`env|grep "..mn"|awk -F"=" '{print $2}'`
Im not able to understand, what exactly it is doing :confused:
Any help would be useful for me.
Lokesha (4 Replies)
Hi,
I have line in input file as below:
3G_CENTRAL;INDONESIA_(M)_TELKOMSEL;SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL
My expected output for line in the file must be :
"1-Radon1-cMOC_deg"|"LDIndex"|"3G_CENTRAL|INDONESIA_(M)_TELKOMSEL"|LAST|"SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL"
Can someone... (7 Replies)
Hi Experts,
I am executing "svn" checkout command through my java code on a freeBSD machine. SVN checkout gets started , but when I run "top" command on my freebsd machine, I have observed that "svn" processes are stuck in "pipewr" state.
Any pointer for this problem?
Thanks,
akash (0 Replies)
Hi Experts,
I am executing "svn" checkout command through my java code on a freeBSD machine. SVN checkout gets started , but when I run "top" command on my freebsd machine, I have observed that "svn" processes are stuck in "pipewr" state.
Any pointer for this problem?
Thanks,
akash (0 Replies)
How to use "mailx" command to do e-mail reading the input file containing email address, where column 1 has name and column 2 containing “To” e-mail address
and column 3 contains “cc” e-mail address to include with same email.
Sample input file, email.txt
Below is an sample code where... (2 Replies)
Hi Community,
i have one M5000 spare machine which was handled by support team. they told me that it is gone completely .
i have checked the status. before it was showing MBU_B degraded. i updated to latest firmware and , resetted the xscf and now this is showing as normal.
MBU_B... (5 Replies)
Hi all, I have a LUN that is in "Online Busy" when I issue the dev_gestate subcommand of luxadm:
root@es088wb6:~# luxadm -v -e dev_getstate /dev/rdsk/c21t50050763090887FEd4s2
phys path = "/devices/pci@6c0/pci@1/pci@0/pci@4/SUNW,qlc@0/fp@0,0/ssd@w50050763090887fe,4:c,raw"
... (5 Replies)
Hello.
System : opensuse leap 42.3
I have a bash script that build a text file.
I would like the last command doing :
print_cmd -o page-left=43 -o page-right=22 -o page-top=28 -o page-bottom=43 -o font=LatinModernMono12:regular:9 some_file.txt
where :
print_cmd ::= some printing... (1 Reply)
Discussion started by: jcdole
1 Replies
LEARN ABOUT BSD
kill
KILL(1) General Commands Manual KILL(1)NAME
kill - terminate a process with extreme prejudice
SYNOPSIS
kill [ -sig ] processid ...
kill -l
DESCRIPTION
Kill sends the TERM (terminate, 15) signal to the specified processes. If a signal name or number preceded by `-' is given as first argu-
ment, that signal is sent instead of terminate (see sigvec(2)). The signal names are listed by `kill -l', and are as given in
/usr/include/signal.h, stripped of the common SIG prefix.
The terminate signal will kill processes that do not catch the signal; `kill -9 ...' is a sure kill, as the KILL (9) signal cannot be
caught. By convention, if process number 0 is specified, all members in the process group (i.e. processes resulting from the current
login) are signaled (but beware: this works only if you use sh(1); not if you use csh(1).) Negative process numbers also have special
meanings; see kill(2) for details.
The killed processes must belong to the current user unless he is the super-user.
The process number of an asynchronous process started with `&' is reported by the shell. Process numbers can also be found by using ps(1).
Kill is a built-in to csh(1); it allows job specifiers of the form ``%...'' as arguments so process id's are not as often used as kill
arguments. See csh(1) for details.
SEE ALSO csh(1), ps(1), kill(2), sigvec(2)BUGS
A replacement for ``kill 0'' for csh(1) users should be provided.
4th Berkeley Distribution April 20, 1986 KILL(1)
04-24-2019
