Sponsored Content
Top Forums UNIX for Dummies Questions & Answers permission to bind a socket to port 843? Post 302313489 by dentar on Tuesday 5th of May 2009 09:42:08 PM
Old 05-05-2009
Sadly, you are likely stuck starting up as root.

Other daemons start up as root, then listen to their < 1024 port, then they change user id to the user that they are supposed to be for the rest of the session.

The only other easy alternative is to choose a higher port number.
 

10 More Discussions You Might Find Interesting

1. Programming

socket on serial port

Does anyone know if it's possible to send socket by a serial port ? If yes, how can I find on Irix the value of my serial ports to use with this function : serverSockAddr.sin_port = ? Thanks for all responses ! Kintoo (2 Replies)
Discussion started by: kintoo
2 Replies

2. Solaris

How to allow nonroot user to bind to port 80

We are making some changes, and are now using Weblogic as the webserver on one of my projects. I would like for the non root user running Weblogic to be able to bind to port 80. (10 Replies)
Discussion started by: 98_1LE
10 Replies

3. UNIX for Dummies Questions & Answers

Socket programming:One server two port

I want my server socket to listen on two ports in my machine. How do i achieve it? I will have two clients one connecting to 1 port and another to a different port. So my server needs to listen to both. Thanks. (1 Reply)
Discussion started by: abc.working
1 Replies

4. Programming

Cloning a socket connection, using other port numbers

Hello everybody, I've coded a multi-client server based on internet sockets using the scheme listen on port X-accept-fork, exactly like beej's guide At some point I would like to establish a secondary connection between a client and the server-child serving him. I was considering the... (4 Replies)
Discussion started by: jonas.gabriel
4 Replies

5. UNIX for Dummies Questions & Answers

Socket bind fails

Hi, 1 more new comer with a small problem. I have a Java socket program which tries to bind to a particular socket. It works fine with windows. But in Linux, it says 'address in use'. I tried 'netstat' to find if the port is being used. But it is free. Can anyone help plz? (0 Replies)
Discussion started by: ronyantony
0 Replies

6. Shell Programming and Scripting

Python: Bind to port 80 as root, then drop privileges?

I have written a small web server in Python, and now I would like to run it on port 80, but in order to be able to bind to a port below 1024 I need to have root privileges. I don't want to run the server as root, though. How can I bind to port 80 as root and then drop root privileges? Thankful... (0 Replies)
Discussion started by: Ilja
0 Replies

7. Programming

GetLastError API for socket/bind failure in VxWorks 5.4

Can anyone tell what is the system API for VxWorks which is used to find GetLastError() for socket/bind failure. I need to use it in some VxWorks application and need to call GetLastError but I'm not sure about the correct API. Thanks in advance (1 Reply)
Discussion started by: anilgurwara
1 Replies

8. Programming

Using socket to test a TCP port

Hello, I'm trying to write a small c application to test a tcp port. This works fine for the most part but the default timeout on the connect is very long. I have been reading many posts but and it looks like I need to set the socket to be non-blocking and poll for a result. I have been totally... (2 Replies)
Discussion started by: tjones1105
2 Replies

9. Shell Programming and Scripting

Script to bind to socket

i need to come up with a script that when run from the command line, it will bind to a socket, and listen for tcp connections on a certain port. something like: ### ./connection_listener 5666 i found the following script on the web but when i run it, it complains about "accept" not being... (1 Reply)
Discussion started by: SkySmart
1 Replies

10. IP Networking

Get process id and port from the socket

Hello, Please help me in getting the process id and the port number from the socket netstat -Aan|grep -i closed f100050010b133b8 tcp 0 0 *.* *.* CLOSED f1000500119b53b8 tcp4 0 0 *.* *.* ... (3 Replies)
Discussion started by: Vishal_dba
3 Replies
SOCKET(1)                                                     General Commands Manual                                                    SOCKET(1)

NAME
socket - create a TCP or a UNIX domain socket and connect to stdin/out SYNOPSIS
socket [ -bcfqrvw ] [ -p command ] [ -B local address ] host port socket [ -bcfqrvw ] [ -p command ] /path socket [ -bcfqrvw ] [ -p command ] [ -B local address ] -s [ -l ] port socket [ -bcfqrvw ] [ -p command ] -s [ -l ] /path DESCRIPTION
Socket creates an Internet domain TCP or a UNIX domain stream socket and connects it to stdin and stdout. The host argument can be an Internet number in dot-notation (like ``130.149.28.10'') or a domain name. In this case it must be possible to resolve the name to a valid Internet address with gethostbyname(3). The port argument can be a port number or a service name which can be mapped to a port number by getservbyname(3). If an UNIX domain socket is wanted to be created instead of an Internet socket, specify the path instead of an internet (canonical domain named or dot-notated) host. The hostname is treated as a pathname if contains at least a single slash. I.e. if one wants to create or connect to a socket in the current directory, use ./filename to specify the connection point. OPTIONS
-b (background) The program forks itself into the background, detaches from its controlling tty, closes the file descriptors associated with the tty, and changes its current directory to the root directory. -B (local address) This option specifies which local address to binded to when making a connection. -c (crlf) Linefeed characters (LF) are converted to a Carriage Return Linefeed sequence (CRLF) when written to the socket. CRLF sequences read from the socket are converted to a single LF. -f (fork) When a server connection has been accepted, a separate process is forked to handle the connection in background. -l (loop) (only valid with -s) After a connection has been closed, another connection is accepted. -p (program) The specified command is executed for each connection. Its standard input, standard output, and standard error channels are con- nected to the socket. Command can be any shell command since it is passed to /bin/sh. -q (quit) The connection is closed when an end-of-file condition occurs on standard input. -r (read only) No data is read from standard input and written to the socket. -s (server) A server socket is created. A hostname argument is not required of Internet sockets, only the port number but a pathname is required for UNIX domain sockets. -v (verbose) Messages about connections etc. are issued to stderr. -w (write only) No data is read from the socket and written to the standard output. -version Socket prints its version ID and terminates. This must be the first argument to have an effect. EXAMPLES
The command socket -v coma.cs.tu-berlin.de nntp connects to the nntp port (port 119) of coma.cs.tu-berlin.de (130.149.28.10). The command socket -sl 3425 creates a server socket on port 3425 on the local host and waits for a connection. After a connection has been closed, a new connection is accepted. The command socket -wslqvp "echo Socket! " 1938 creates a server socket on port 1938 on the local host and waits for a connection. When a connection is accepted, the string "Socket!" is written to the socket. No data is read from the socket and written to the finger program. The connection is closed when an end-of-file condition at the standard output of the program occurs. Then a new connection is accepted. DIAGNOSTICS
Lots of diagnostics for failed system calls. unknown host host host's address could not be resolved. Signal signal caught, exiting Socket exits on any signal other than SIGTSTP, SIGCONT, SIGCLD, SIGQUIT. A non-zero exit code is returned if socket terminates due to an error condition or a signal. SEE ALSO
ip(7), tcp(7), unix(7), accept(2), bind(2), listen(2), connect(2), socket(2), gethostbyname(3), getservbyname(3) BUGS
socket -p terminates due to a SIGPIPE signal when there is more data from the socket available than the executed program wants to read. Please report any other bugs to the author. VERSION
This manual page describes Socket-1.1. AUTHOR
Juergen Nickelsen <nickel@cs.tu-berlin.de> Aug 6, 1992 SOCKET(1)
All times are GMT -4. The time now is 07:28 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy