01-11-2008
problem with accept() on Fedora 8
hi,
accept() seems to be still blocking after socket is being closed on our Fedora 8 build. not sure if this is a common problem because i have never experienced this on any other platforms, however i have seen someone else having this issue on Redhat 7 and 9. so is there a socket option fedora is setting differently or anyone know an appropriate method to get that thread out of the accept?
thanks in advance
10 More Discussions You Might Find Interesting
1. HP-UX
Hi, there
On HP-UX IA server, when calling 'accept' function in my program, the server never wait the client's connection. Each time, it accepted the request from IP address 0.0.0.0 even there is no client's connection. The server program looks like :
main()
{
.
.
.... (4 Replies)
Discussion started by: Frank2004
4 Replies
2. Shell Programming and Scripting
Hello,
I stop a process with kill -s SIGSTOP, but when I try to restart it with kill -s SIGCONT it do nothing.
I use Fedora Core 4.
Thank you a lot (1 Reply)
Discussion started by: Nene
1 Replies
3. Gentoo
HI,
I installed fedora core 6 on my inspiron 1501. After I boot it gives me the following error,
PCI: BIOS BUG #81(00000000) found. (1 Reply)
Discussion started by: linuxuser
1 Replies
4. Linux
hi all
i am currently using fedora core 3 . i downloaded the iso image of fedora core 6 but after installing the fedora core 6 . while starting linux it gives a error saying init is been killed .
wht is happened?
thank u (3 Replies)
Discussion started by: nageshrk
3 Replies
5. Linux
Problem about Fedora directory permission,can anyone help me?
In fedora,I have two ordinary user named user1&user2 in different
groups,when I logined user1 and created a dir named test/ in '/home/
user1/',and do 'chmod 750 test',so when 'ls -l',it appears 'drwxr-
x---' for 'test',but when I... (3 Replies)
Discussion started by: zhouq3132
3 Replies
6. Red Hat
Hi guys
i installed fedora 9 in my system.
i installed perl-devel rpm and perl-5.10.0 rpm.
But perlcc not in /usr/bin/ directory.But perl,perldoc binaris installed.
i am new one for linux. (3 Replies)
Discussion started by: viveksnv
3 Replies
7. SuSE
I appeal to all those of you that have experience with Fedora 9 for help. I am trying to install a suite of software which tries to make changes to the /etc/dhcpd.conf file. After the changes have been made the dhcpd service will not start and the original conf file is restored. However dhcpd... (1 Reply)
Discussion started by: johnf
1 Replies
8. Linux
Hi there, I'm having a bit of a strange problem which I would appreciate some help with.
The Problem:
I have two external hard drives, but I'm borrowing one off my parents to copy data too (one of mine, which is identical to theirs - WD MyBook 300g - is on its way out).
Fedora 9 recognizes... (3 Replies)
Discussion started by: lasthidingplace
3 Replies
9. Red Hat
Hi,
I am having booting issue with Fedora 11 x86_64 (64-bit version) on my laptop.
Laptop configuration is as below:
OS : Windows Vista Home Premium (64-bit)
Processor : Intel Core 2 Duo T6400 2.0 GHz
RAM : 4 GB
Tried following different way for installation:
1. Installed Fedora 11 on... (2 Replies)
Discussion started by: r2kv2k
2 Replies
10. Linux
Hello,
Can anyone please explain HOW Crontab i.e. job scheduling daemon works in Fedora and CentOS or any Linux platform(Ubuntu)....
What are the points that i have to take care of if have to include a script to be run at a specific scheduled time.
URGENT reply requested. Please help (1 Reply)
Discussion started by: Vabiosis
1 Replies
LEARN ABOUT ULTRIX
accept
accept(2) System Calls Manual accept(2)
Name
accept - accept a connection on a socket
Syntax
#include <sys/types.h>
#include <sys/socket.h>
accept(s, addr, addrlen)
int ns, s;
struct sockaddr *addr;
int *addrlen;
Description
The system call accepts a connection on a socket. The argument s is a socket that has been created with the call, bound to an address with
the call and is listening for connections after a call. The system call extracts the first connection on the queue of pending connections,
creates a new socket with the same properties of s and allocates a new file descriptor, ns, for the socket. If no pending connections are
present on the queue, and the socket is not marked as nonblocking, blocks the caller until a connection is present. If the socket is
marked nonblocking and no pending connections are present on the queue, returns an error. The accepted socket, ns, cannot be used to
accept more connections. The original socket s remains open.
The argument addr is a result parameter that is filled in with the address of the connecting entity, as known to the communications layer.
The exact format of the addr parameter is determined by the domain in which the communication is occurring. The addrlen is a value-result
parameter; it should initially contain the amount of space pointed to by addr. On return, addr contains the actual length in bytes of the
address returned. This call is used with connection-based socket types, currently with SOCK_STREAM.
You can use the call for the purposes of doing an call by selecting the socket for reading.
Return Values
The call returns -1 on error. If the call succeeds, it returns a non-negative integer which is a descriptor for the accepted socket.
Diagnostics
The call fails if:
[EBADF] The descriptor is invalid.
[ENOTSOCK] The descriptor references a file, not a socket.
[EOPNOTSUPP] The referenced socket is not of type SOCK_STREAM.
[EFAULT] The addr parameter is not in a writable part of the user address space.
[EWOULDBLOCK] The socket is marked nonblocking and no connections are present to be accepted.
See Also
bind(2), connect(2), listen(2), select(2), socket(2)
accept(2)