01-03-2008
Binary Get Hanged
Hi,
In our product we have use binary that fork the child process to make proxy the connection to device.But recently when we try to connect new configured device several times it get handed and binary stop making further new connection to device.it required to RESTART the services to make binary work.
please suggest what are the possible causes that make binary hang.also now we are trying to replicate the same scenerio but it not happen the same.we are unable to create the same scenerio.It is working fine now.Is network problem may be one of the reason that make binany hang ???
Thanks
Anand P.
10 More Discussions You Might Find Interesting
1. AIX
Hi,
Can anyone help me to find out how I can get more detail about child process where it hanged and what information it needs to end. Same scripts runs on Solaris work fine!
Thanks for the help (0 Replies)
Discussion started by: techidada
0 Replies
2. Shell Programming and Scripting
Hi,
Problem with Sendmail
When I receive the mail in my outlook, (sent using sendmail ) , Outlook is not working properly( its getting hanged).I am using the script which is available in this forum. The following are the headers that are getting generated . Sendmail is running on SunOS... (5 Replies)
Discussion started by: Srini75
5 Replies
3. UNIX for Advanced & Expert Users
HI,
I have a Fedora running box. I am not able to ping/login. I guess it got hanged.
Can any one help me how to login to that box with out restart? (8 Replies)
Discussion started by: praveen_b744
8 Replies
4. Shell Programming and Scripting
Hi Everyone,
I have written a script to automate the docbase cleanup process on every weekly basis. That is in this script i have to shutdown the docbase and then kill all the process that are hanged except one process(epic process) and need to delete some log files and then i have to start the... (8 Replies)
Discussion started by: Sheethal
8 Replies
5. Linux
Hi,
In our product we have use binary that fork the child process to make proxy the connection to device.But recently when we try to connect new configured device several times it get handed and binary stop making further new connection to device.it required to RESTART the services to make... (1 Reply)
Discussion started by: Anand Prakash
1 Replies
6. Solaris
Hi,
My process is visible in 'ps' command but actually it is not working or it got hanged. This process is not generating any log. Now How can I know that my process got hanged.
Please help. (2 Replies)
Discussion started by: sanjay1979
2 Replies
7. Solaris
Hi ,
I need your help on the my unix (solaris system was down) when i enter console login ans password could not opearte their application .
i tried reboot many times but still same error was occurred.
Please refer the attcahed file , how i need to solve this issue?:wall:
I 'm not... (2 Replies)
Discussion started by: Thamil
2 Replies
8. Solaris
Hello people,
I got one problem with a script.
I have a script which runs every five mins and in the script an ftp process is invoked which sends files to a particular location.
The problem is that the ftp process hangs every now and then which causes the whole script to hang.
As the... (4 Replies)
Discussion started by: m_usmanayub
4 Replies
9. Shell Programming and Scripting
Hello *nix specialists,
Im working for a non profit organisation in Germany to transport DSL over WLAN to people in areas without no DSL. We are using Linksys WRT 54 router with DD-WRT firmware There are at the moment over 180 router running but we have to change some settings next time. So my... (7 Replies)
Discussion started by: digidax
7 Replies
10. UNIX for Advanced & Expert Users
Hi,
I have recently changed the port speed to 1000 Mbps, auto negotiation ON from 100 Mbps auto negotiation OFF. At a particular time in the night, various other nodes FTP few big file to this node. At that particular moment when the other node start FTPing, the server becomes slow and is kind... (1 Reply)
Discussion started by: brij123
1 Replies
NDIS(4) BSD Kernel Interfaces Manual NDIS(4)
NAME
ndis -- NDIS miniport driver wrapper
SYNOPSIS
options NDISAPI
device ndis
device wlan
DESCRIPTION
The ndis driver is a wrapper designed to allow binary Windows(R) NDIS miniport network drivers to be used with FreeBSD. The ndis driver is
provided in source code form and must be combined with the Windows(R) driver supplied with your network adapter. The ndis driver uses the
ndisapi kernel subsystem to relocate and link the Windows(R) binary so that it can be used in conjunction with native code. The ndisapi sub-
system provides an interface between the NDIS API and the FreeBSD networking infrastructure. The Windows(R) driver is essentially fooled
into thinking it is running on Windows(R). Note that this means the ndis driver is only useful on x86 machines.
To build a functional driver, the user must have a copy of the driver distribution media for his or her card. From this distribution, the
user must extract two files: the .SYS file containing the driver binary code, and its companion .INF file, which contains the definitions for
driver-specific registry keys and other installation data such as device identifiers. These two files can be converted into a kernel module
file using the ndisgen(8) utility. This file contains a binary image of the driver plus registry key data. When the ndis driver loads, it
will create sysctl(3) nodes for each registry key extracted from the .INF file.
The ndis driver is designed to support mainly Ethernet and wireless network devices with PCI, PCMCIA and USB bus attachments. (Cardbus
devices are also supported as a subset of PCI.) It can support many different media types and speeds. One limitation however, is that there
is no consistent way to learn if an Ethernet device is operating in full or half duplex mode. The NDIS API allows for a generic means for
determining link state and speed, but not the duplex setting. There may be driver-specific registry keys to control the media setting which
can be configured via the sysctl(8) command.
DIAGNOSTICS
ndis%d: watchdog timeout A packet was queued for transmission and a transmit command was issued, however the device failed to acknowledge
the transmission before a timeout expired.
SEE ALSO
altq(4), arp(4), netintro(4), ng_ether(4), ifconfig(8), ndis_events(8), ndiscvt(8), ndisgen(8), wpa_supplicant(8)
NDIS 5.1 specification, http://www.microsoft.com.
HISTORY
The ndis device driver first appeared in FreeBSD 5.3.
AUTHORS
The ndis driver was written by Bill Paul <wpaul@windriver.com>.
BSD March 14, 2010 BSD