03-14-2005
Thanks a lot for the reply. It solved the problem.
Thanks.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
Is there any way i can know the association between sockets and the processes which created them.
:confused: (5 Replies)
Discussion started by: soorajmu
5 Replies
2. IP Networking
hello,
how can we create a domain in unix operating systems. By domain i mean which is used to maintain remote user logins and etc.
cheers (1 Reply)
Discussion started by: vibhory2j
1 Replies
3. UNIX for Dummies Questions & Answers
Hi,
Can I make a UNIX or LINUX machine a member of MS Active Directory 2003?
How?
Regards
Leo (4 Replies)
Discussion started by: Teamplay
4 Replies
4. UNIX for Dummies Questions & Answers
Hiya,
what is the exact command to add a Unix machine to the existing domain?
Is this command different for Linux/HP-Ux?
thanks (3 Replies)
Discussion started by: Wize
3 Replies
5. UNIX for Advanced & Expert Users
If I use sockets for IPC, and can easily distribute my applications.
UNIX Message Queues are local to the processor.
As I understand it, Message Queues still incur system call overhead, just like socket calls.
What advantage does a UNIX Message Queue provide versus a TCP or UDP Socket,... (2 Replies)
Discussion started by: zen29sky
2 Replies
6. Shell Programming and Scripting
Hi all,
When parameters are passed to the shell script, they are dereferenced by their position. For example,
I call myTest.sh and pass two parameters param1 and param2 as following:
./myTest.sh param1 param2
In the script, myTest.sh, I refer to first parameter (param1 ) as $1 and second... (1 Reply)
Discussion started by: sonaluphale
1 Replies
7. What is on Your Mind?
I wonder when UNIX will be a OS, will have a single version. (1 Reply)
Discussion started by: abhishek0216
1 Replies
8. UNIX for Advanced & Expert Users
Is there a performance advantage of one of these over the other? Obviously, it makes no sense to use normal TCP sockets or UDP sockets w/ the overhead they carry. But what about UNIX domain sockets vs FIFOs? I'd think they'd be very similar, in terms of performance and in terms of how they're... (2 Replies)
Discussion started by: mgessner
2 Replies
9. Shell Programming and Scripting
I had issues with processes locking up. This script checks for processes and kills them if they are older than a certain time.
Its uses some functions you'll need to define or remove, like slog() which I use for logging, and is_running() which checks if this script is already running so you can... (0 Replies)
Discussion started by: sukerman
0 Replies
10. UNIX for Dummies Questions & Answers
Hi,
i understood that there are several type of sockets: TCP, UDP & Unix.
i wondered, what is the performance advantages of unix socket of the other types?
isn't it equal to use UDP with localhost as destination over unix socket?
Thanks in advance,
Sariel (1 Reply)
Discussion started by: sarielz
1 Replies
LEARN ABOUT MOJAVE
curlopt_unix_socket_path
CURLOPT_UNIX_SOCKET_PATH(3) curl_easy_setopt options CURLOPT_UNIX_SOCKET_PATH(3)
NAME
CURLOPT_UNIX_SOCKET_PATH - set Unix domain socket
SYNOPSIS
#include <curl/curl.h>
CURLcode curl_easy_setopt(CURL *handle, CURLOPT_UNIX_SOCKET_PATH, char *path);
DESCRIPTION
Enables the use of Unix domain sockets as connection endpoint and sets the path to path. If path is NULL, then Unix domain sockets are dis-
abled. An empty string will result in an error at some point, it will not disable use of Unix domain sockets.
When enabled, curl will connect to the Unix domain socket instead of establishing a TCP connection to a host. Since no TCP connection is
created, curl does not need to resolve the DNS hostname in the URL.
The maximum path length on Cygwin, Linux and Solaris is 107. On other platforms it might be even less.
Proxy and TCP options such as CURLOPT_TCP_NODELAY(3) are not supported. Proxy options such as CURLOPT_PROXY(3) have no effect either as
these are TCP-oriented, and asking a proxy server to connect to a certain Unix domain socket is not possible.
The application does not have to keep the string around after setting this option.
DEFAULT
Default is NULL, meaning that no Unix domain sockets are used.
PROTOCOLS
All protocols except for file:// and FTP are supported in theory. HTTP, IMAP, POP3 and SMTP should in particular work (including their
SSL/TLS variants).
EXAMPLE
Given that you have an nginx server running, listening on /tmp/nginx.sock, you can request a HTTP resource with:
curl_easy_setopt(curl_handle, CURLOPT_UNIX_SOCKET_PATH, "/tmp/nginx.sock");
curl_easy_setopt(curl_handle, CURLOPT_URL, "http://localhost/");
If you are on Linux and somehow have a need for paths larger than 107 bytes, you could use the proc filesystem to bypass the limitation:
int dirfd = open(long_directory_path_to_socket, O_DIRECTORY | O_RDONLY);
char path[108];
snprintf(path, sizeof(path), "/proc/self/fd/%d/nginx.sock", dirfd);
curl_easy_setopt(curl_handle, CURLOPT_UNIX_SOCKET_PATH, path);
/* Be sure to keep dirfd valid until you discard the handle */
AVAILABILITY
Since 7.40.0.
RETURN VALUE
Returns CURLE_OK if the option is supported, and CURLE_UNKNOWN_OPTION if not.
SEE ALSO
CURLOPT_OPENSOCKETFUNCTION(3), unix(7),
libcurl 7.54.0 December 21, 2016 CURLOPT_UNIX_SOCKET_PATH(3)