04-22-2019
D state is "device waiting" and is a bit nasty.
Such a process cannot be killed.
It makes sense to guess the blocking device, and fix it. Once fixed, the proceses will leave the D state and continue.
These 2 Users Gave Thanks to MadeInGermany For This Post:
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 CENTOS
enum_wimax_st
ENUM
WIMAX_ST(9) Linux Networking ENUM WIMAX_ST(9)
NAME
enum_wimax_st - The different states of a WiMAX device
SYNOPSIS
enum wimax_st {
__WIMAX_ST_NULL,
WIMAX_ST_DOWN,
__WIMAX_ST_QUIESCING,
WIMAX_ST_UNINITIALIZED,
WIMAX_ST_RADIO_OFF,
WIMAX_ST_READY,
WIMAX_ST_SCANNING,
WIMAX_ST_CONNECTING,
WIMAX_ST_CONNECTED,
__WIMAX_ST_INVALID
};
CONSTANTS
__WIMAX_ST_NULL
The device structure has been allocated and zeroed, but still wimax_dev_add hasn't been called. There is no state.
WIMAX_ST_DOWN
The device has been registered with the WiMAX and networking stacks, but it is not initialized (normally that is done with 'ifconfig
DEV up' [or equivalent], which can upload firmware and enable communications with the device). In this state, the device is powered
down and using as less power as possible. This state is the default after a call to wimax_dev_add. It is ok to have drivers move
directly to WIMAX_ST_UNINITIALIZED or WIMAX_ST_RADIO_OFF in _probe after the call to wimax_dev_add. It is recommended that the driver
leaves this state when calling 'ifconfig DEV up' and enters it back on 'ifconfig DEV down'.
__WIMAX_ST_QUIESCING
The device is being torn down, so no API operations are allowed to proceed except the ones needed to complete the device clean up
process.
WIMAX_ST_UNINITIALIZED
[optional] Communication with the device is setup, but the device still requires some configuration before being operational. Some
WiMAX API calls might work.
WIMAX_ST_RADIO_OFF
The device is fully up; radio is off (wether by hardware or software switches). It is recommended to always leave the device in this
state after initialization.
WIMAX_ST_READY
The device is fully up and radio is on.
WIMAX_ST_SCANNING
[optional] The device has been instructed to scan. In this state, the device cannot be actively connected to a network.
WIMAX_ST_CONNECTING
The device is connecting to a network. This state exists because in some devices, the connect process can include a number of
negotiations between user space, kernel space and the device. User space needs to know what the device is doing. If the connect
sequence in a device is atomic and fast, the device can transition directly to CONNECTED
WIMAX_ST_CONNECTED
The device is connected to a network.
__WIMAX_ST_INVALID
This is an invalid state used to mark the maximum numeric value of states.
DESCRIPTION
Transitions from one state to another one are atomic and can only be caused in kernel space with wimax_state_change. To read the state, use
wimax_state_get.
States starting with __ are internal and shall not be used or referred to by drivers or userspace. They look ugly, but that's the point --
if any use is made non-internal to the stack, it is easier to catch on review.
All API operations [with well defined exceptions] will take the device mutex before starting and then check the state. If the state is
__WIMAX_ST_NULL, WIMAX_ST_DOWN, WIMAX_ST_UNINITIALIZED or __WIMAX_ST_QUIESCING, it will drop the lock and quit with -EINVAL, -ENOMEDIUM,
-ENOTCONN or -ESHUTDOWN.
The order of the definitions is important, so we can do numerical comparisons (eg: < WIMAX_ST_RADIO_OFF means the device is not ready to
operate).
COPYRIGHT
Kernel Hackers Manual 3.10 June 2014 ENUM WIMAX_ST(9)