These are the well known ports from IANA. Basically it means if you use one of these
adhoc you run the risk of breaking something - now or next week. Just because a port is unused right now does not mean it won't get used again soon.
Is there a reason you have to use low number ports?
Try something like this:
Code:
LASTPORT=32767
ss | awk ' /\*/ {print $6 } > portlist.txt
getport {
result="FAIL"
for (( i=8193; i<$LASTPORT; i++))
do
grep -q "$i" portlist.txt && continue
result="$i"
break
done
echo "$result"
}
# usage
port=$( getport )
if [ "$port" = "FAIL" ] ; then
echo "no ports available"
exit
fi
# use the port number here
You could also create an array (port based) on the awk output and search through the array rather than using grep. Use the mapfile command, which creates an array named MAPFILE with every port number in it. You can also use associative arrays to speed up your search. None of this is really useful except when you are creating lots of ports.
I want to write a server application that would accept HTTP requests from client.
The server would be on a machine that has no connection to the INTERNET.
The clients that would be posting their HTTP requests would be doing so through webbrowser .Thus it would be sort of intranet application.... (0 Replies)
Hello Mentors!
I am a new here in the furom, i hope somebody can understand my problem.
Basically we have an application here called unigraphics and being installed per station and the setup is look like this.
1. installed unigraphics UGNX3 version on every station
2. some are installed in... (1 Reply)
Hello
im using sunos im trying to lock down application that taking my port
when Im doing "netstat -in | grep 8080"
Is gives me the indication that the port is taken but no indication who is taken the port.
How can I find out who is taking my port?
Thanks allot (7 Replies)
Dear Sir,
i m going to use NP5610-16 moxa device for multiport serial communication.
i m using fedora-core 6 o.s.
after installation it will detect serial ports as /dev/ttyr0,/dev/ttyr1...ttyr32.
there are total 32 com ports.
now i want to write application which monitor all serial ports and... (6 Replies)
Hi All,
I have two MQ (port) 1414 established (going out)
$ netstat -an | grep 1414
tcp 0 0 0.0.0.0:1414 0.0.0.0:* LISTEN
tcp 0 0 20.76.1.1:32855 142.8.1.3:1414 ESTABLISHED
tcp 0 0... (2 Replies)
Hi,
is there any command to findout that which application is using the particular port.
or whether any port is occupied with the specfic process id ? (4 Replies)
Hi Everyone,
In my environment, I have few T5220. On the iLOM Management Card, I have both Network and Serial port are cabled, I don't have any issues while I try to connect using Network Management port, but when I try to connect the serial port for the same server which is actually connected... (3 Replies)
Hello,
I have an unloaded T5140 machine and want to access the ILOM for the first time and subsequently the network port after that., and then load Solaris 10 the final January 2011 build.
The first part is what confuses me -the cabling.
I am coming from a Windows machine (w/appropriate... (5 Replies)
please find the below o/p for your reference
bash-3.00# fcinfo hba-port
HBA Port WWN: 21000024ff295a34
OS Device Name: /dev/cfg/c2
Manufacturer: QLogic Corp.
Model: 375-3356-02
Firmware Version: 05.03.02
FCode/BIOS Version: BIOS: 2.02; fcode: 2.01;... (3 Replies)
Discussion started by: sb200
3 Replies
LEARN ABOUT SUSE
parport_register_port
PARPORT_REGISTER_POR(9) Parallel Port Devices PARPORT_REGISTER_POR(9)NAME
parport_register_port - register a parallel port
SYNOPSIS
struct parport * parport_register_port(unsigned long base, int irq, int dma, struct parport_operations * ops);
ARGUMENTS
base
base I/O address
irq
IRQ line
dma
DMA channel
ops
pointer to the port driver's port operations structure
DESCRIPTION
When a parallel port (lowlevel) driver finds a port that should be made available to parallel port device drivers, it should call
parport_register_port. The base, irq, and dma parameters are for the convenience of port drivers, and for ports where they aren't
meaningful needn't be set to anything special. They can be altered afterwards by adjusting the relevant members of the parport structure
that is returned and represents the port. They should not be tampered with after calling parport_announce_port, however.
If there are parallel port device drivers in the system that have registered themselves using parport_register_driver, they are not told
about the port at this time; that is done by parport_announce_port.
The ops structure is allocated by the caller, and must not be deallocated before calling parport_remove_port.
If there is no memory to allocate a new parport structure, this function will return NULL.
COPYRIGHT Kernel Hackers Manual 2.6. July 2010 PARPORT_REGISTER_POR(9)