04-23-2019
Quote:
Originally Posted by
MadeInGermany
Actually I expect gdb to also get hung when attaching it to a process in D state. But it's worth a trial.
If processes are permanently hung in cifs_reconnect_tcon then it looks like a kernel bug (or a missing interrupt/timeout feature).
Is your kernel at the latest patch level?
I agree.
He has nothing to lose to at least try to attach with
gdb if he really does not want to reboot.
He might get lucky
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
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)
Discussion started by: Lokesha
4 Replies
2. Red Hat
Friends ,
Anybody plz tell me what is the basic difference between "service" , "process" and " daemon" ?
Waiting for kind reply .. .. (1 Reply)
Discussion started by: shipon_97
1 Replies
3. Shell Programming and Scripting
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)
Discussion started by: shis100
7 Replies
4. UNIX for Advanced & Expert Users
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)
Discussion started by: akash.mahakode
0 Replies
5. BSD
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)
Discussion started by: akash.mahakode
0 Replies
6. UNIX for Dummies Questions & Answers
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)
Discussion started by: asjaiswal
2 Replies
7. Solaris
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)
Discussion started by: bentech4u
5 Replies
8. Solaris
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)
Discussion started by: ludiegu
5 Replies
9. Shell Programming and Scripting
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 OPENDARWIN
_exit
EXIT(2) BSD System Calls Manual EXIT(2)
NAME
_exit -- terminate the calling process
SYNOPSIS
#include <unistd.h>
void
_exit(int status);
DESCRIPTION
The _exit() function terminates a process with the following consequences:
o All of the descriptors open in the calling process are closed. This may entail delays, for example, waiting for output to drain; a
process in this state may not be killed, as it is already dying.
o If the parent process of the calling process has an outstanding wait call or catches the SIGCHLD signal, it is notified of the calling
process's termination and the status is set as defined by wait(2).
o The parent process-ID of all of the calling process's existing child processes are set to 1; the initialization process (see the DEFINI-
TIONS section of intro(2)) inherits each of these processes.
o If the termination of the process causes any process group to become orphaned (usually because the parents of all members of the group
have now exited; see ``orphaned process group'' in intro(2)), and if any member of the orphaned group is stopped, the SIGHUP signal and
the SIGCONT signal are sent to all members of the newly-orphaned process group.
o If the process is a controlling process (see intro(2)), the SIGHUP signal is sent to the foreground process group of the controlling ter-
minal, and all current access to the controlling terminal is revoked.
Most C programs call the library routine exit(3), which flushes buffers, closes streams, unlinks temporary files, etc., before calling
_exit().
RETURN VALUE
_exit() can never return.
SEE ALSO
fork(2), sigaction(2), wait(2), exit(3)
STANDARDS
The _exit function is defined by IEEE Std 1003.1-1988 (``POSIX.1'').
4th Berkeley Distribution June 4, 1993 4th Berkeley Distribution