Sponsored Content
Full Discussion: Threads v/s Connections
Top Forums UNIX for Dummies Questions & Answers Threads v/s Connections Post 35616 by suntan on Tuesday 22nd of April 2003 10:24:45 PM
Old 04-22-2003
Lightbulb Threads v/s Connections

Can someone please explain the difference between a connection and a thread. Any explanation will help!

Thanks
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Establishing connections

Hello there, just a quick question.....Can someone please explain the concept that enables you to establish a connection using the same userId Thanx (1 Reply)
Discussion started by: BigTool4u2
1 Replies

2. UNIX for Dummies Questions & Answers

Killing Connections

Say, for instance, that you are running a website. You are playing around, using netstat, etc. You notice all the people whom are connected to the site. You then wonder if there is a way to kill one or more of these connections. However, they are not PIDs so could you use the kill command? I was... (1 Reply)
Discussion started by: Phobos
1 Replies

3. HP-UX

HP-UX: X connections...?

Hello All, I have 2 qries about X connections on HP-UX : 1.How/where to determine whether "X connections" to the server are controlled. 2. How/where to determine whether "X11 connection" are tunnelled via ssh. 3. How/where to determine the "Time in minutes before unattended X terminals... (0 Replies)
Discussion started by: abhayh
0 Replies

4. UNIX for Advanced & Expert Users

Problems with connections

Hello everybody, Look, im having problems with connections from other server, i must recieve maximus 5 connections from the other server, when I run 'netstat -A | grep <THE_OTHER_SERVER_IP>' I can see how many connections I have already established, but when they open another connection, i mean... (8 Replies)
Discussion started by: Lestat
8 Replies

5. UNIX for Advanced & Expert Users

Threads and Threads Count ?

Hi all, How can I get the list of all Threads and the Total count of threads under a particular process ? Do suggest !! Awaiting for the replies !! Thanks Varun:b: (2 Replies)
Discussion started by: varungupta
2 Replies

6. SCO

UUCP connections

Hi There Is there a maximum number of concurrent incoming uucp connections to a server? SCO Openserver 5.07 Is there a parameter in some config file where this can be changed? Thanx (5 Replies)
Discussion started by: wjace
5 Replies

7. AIX

connections on server

I am using AIX 5.3, its a application server, i am giving the support of OS & Hardware only, now i want to check how many connections are connected to my server, means how many people using my server.:confused: (4 Replies)
Discussion started by: reply.ravi
4 Replies

8. Solaris

Passwordless connections

Hi All! Please help me with this situation: I have 3 servers configured with the following network 10.100.48.xx and I have configured on the passwordless connection, and it is working fine. Now the app vendor ask me to configure a 2nd IP address on each of the 3 servers with a different IP... (4 Replies)
Discussion started by: fretagi
4 Replies

9. Cybersecurity

1780 connections from one IP

Hello, one US IP having 1700+ connections when doing: netstat -tn 2>/dev/null | grep :80 | awk '{print $5}' | cut -d: -f1 | sort | uniq -c | sort -nr | head 1780 * ... * ... * i want to ask how to debug what this IP does? (3 Replies)
Discussion started by: postcd
3 Replies

10. UNIX for Advanced & Expert Users

Network Connections

I have a static IP 47.21.154.146 and two computers which I wish to talk to each other. The two IPs are 198.168.1.5 and 198.168.1.6. How do I do it. For example ls from one computer to the other. TIA (8 Replies)
Discussion started by: Meow613
8 Replies
explain_opendir(3)					     Library Functions Manual						explain_opendir(3)

NAME
explain_opendir - explain opendir(3) errors SYNOPSIS
const char *explain_opendir(const char *pathname); const char *explain_errno_opendir(int errnum, const char *pathname); int errnum, const char *pathname); void explain_message_opendir(char *message, int message_size, void explain_message_errno_opendir(char *message, int message_size, const char *pathname); DESCRIPTION
These functions may be used to explain opendir(3) errors. explain_opendir const char *explain_opendir(const char *pathname); The explain_opendir function is used to obtain an explanation of an error returned by the opendir(3) function. The least the message will contain is the value of strerror(errno), but usually it will do much better, and indicate the underlying cause in more detail. The errno global variable will be used to obtain the error value to be decoded. This function is intended to be used in a fashion similar to the following example: DIR *dp = opendir(pathname); if (!dp) { fprintf(stderr, "%s ", explain_opendir(pathname)); exit(EXIT_FAILURE); } pathname The original pathname, exactly as passed to the opendir(3) system call. Returns: The message explaining the error. This message buffer is shared by all libexplain functions which do not supply a buffer in their argument list. This will be overwritten by the next call to any libexplain function which shares this buffer, including other threads. Note: This function is not thread safe, because it shares a return buffer across all threads, and many other functions in this library. explain_errno_opendir const char *explain_errno_opendir(int errnum, const char *pathname); int errnum, const char *pathname); The explain_errno_opendir function is used to obtain an explanation of an error returned by the opendir(3) function. The least the message will contain is the value of strerror(errnum), but usually it will do much better, and indicate the underlying cause in more detail. This function is intended to be used in a fashion similar to the following example: DIR *dp = opendir(pathname); if (!dp) { int errnum = errno; const char *message = explain_errno_opendir(errnum, pathname); fprintf(stderr, "%s ", message); exit(EXIT_FAILURE); } errnum The error value to be decoded, usually obtained from the errno global variable just before this function is called. This is neces- sary if you need to call any code between the system call to be explained and this function, because many libc functions will alter the value of errno. pathname The original pathname, exactly as passed to the opendir(3) system call. Returns: The message explaining the error. This message buffer is shared by all libexplain functions which do not supply a buffer in their argument list. This will be overwritten by the next call to any libexplain function which shares this buffer, including other threads. Note: This function is not thread safe, because it shares a return buffer across all threads, and many other functions in this library. explain_message_opendir void explain_message_opendir(char *message, int message_size, const char *pathname); The explain_message_opendir function is used to obtain an explanation of an error returned by the opendir(3) function. The least the mes- sage will contain is the value of strerror(errno), but usually it will do much better, and indicate the underlying cause in more detail. The errno global variable will be used to obtain the error value to be decoded. This function is intended to be used in a fashion similar to the following example: DIR *dp = opendir(pathname); if (!dp) { char message[3000]; explain_message_opendir(message, sizeof(message), pathname); fprintf(stderr, "%s ", message); exit(EXIT_FAILURE); } message The location in which to store the returned message. Because a message return buffer has been supplied, this function is thread safe if the buffer is thread safe. message_size The size in bytes of the location in which to store the returned message. pathname The original pathname, exactly as passed to the opendir(3) system call. explain_message_errno_opendir void explain_message_errno_opendir(char *message, int message_size, const char *pathname); The explain_message_errno_opendir function is used to obtain an explanation of an error returned by the opendir(3) function. The least the message will contain is the value of strerror(errnum), but usually it will do much better, and indicate the underlying cause in more detail. This function is intended to be used in a fashion similar to the following example: DIR *dp = opendir(pathname); if (!dp); { int err = errno; char message[3000]; explain_message_errno_opendir(message, sizeof(message), err, pathname); fprintf(stderr, '%s ', message); exit(EXIT_FAILURE); } message The location in which to store the returned message. Because a message return buffer has been supplied, this function is thread safe if the buffer is thread safe. message_size The size in bytes of the location in which to store the returned message. errnum The error value to be decoded, usually obtained from the errno global variable just before this function is called. This is neces- sary if you need to call any code between the system call to be explained and this function, because many libc functions will alter the value of errno. pathname The original pathname, exactly as passed to the opendir(3) system call. COPYRIGHT
libexplain version 0.52 Copyright (C) 2008 Peter Miller AUTHOR
Written by Peter Miller <pmiller@opensource.org.au> explain_opendir(3)
All times are GMT -4. The time now is 10:08 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy