12-21-2006
Typically, ssh will be running on port 22. "echo $(read < /dev/udp/localhost/22)" is gibberish but let's pretend that it reads from that socket and displays a line. In that case, you established a connection to the ssh server and are reading. You would probably display a login prompt but then do nothing else. Then along comes "echo qwerty > /dev/udp/localhost/22". Here you are basicly ignoring incoming data but you sent qwerty as a login name.
When two users on the same system simultaneously do "ssh localhost", they are not in communication with each other. If you are trying to write a client and server you are in the wrong language. I don't see any way to write a server in bash.
10 More Discussions You Might Find Interesting
1. Programming
Hi,
Am very new to socket programming.
When we use UDP sockets to communicate between two processess,
will both the client/server socket be able to send/recv ?
meaning can sendto()/ recvfrom() be used on both server and client?
It could be useful even if anybody provide some link on socket... (1 Reply)
Discussion started by: rvan
1 Replies
2. Programming
Hi all,
I have an application where
there are 5 udp clients/senders which keep sending data to same IP with different port number
can I design my udp server to recieve data from all 5 clients at the same time? how should I use the server address structure? should I use different... (3 Replies)
Discussion started by: shashi
3 Replies
3. UNIX for Dummies Questions & Answers
Hi...Please can someone send me implementation chat application using UDP(socket programming in C). Please send me as soon as possible. Thanks in advance. (2 Replies)
Discussion started by: unsweety
2 Replies
4. UNIX for Dummies Questions & Answers
hi,
i have a source code for 1 server and 2 clients ...but the clients are not able to send data..1 server only receives data from clients and forwards to any other client, the data is in the buffer.....please help... thank you in advance.....
/**********client1***************/
// Here Data... (1 Reply)
Discussion started by: unsweety
1 Replies
5. IP Networking
Hello !
I seem to have the same problem as in https://www.unix.com/ip-networking/91203-inaddr_any-opposite.html#post302262417
But I can't find a solution.
I have a UDP server socket bound to 0.0.0.0. The server hosts the addresses IP1, IP2 and IP3. I get an incoming request to IP1. I use... (1 Reply)
Discussion started by: steinwej
1 Replies
6. Programming
could somebody give me hand programming the attached request.
my code isn't complete and i do not really understand how should i implement that. (1 Reply)
Discussion started by: makaveli_
1 Replies
7. Programming
hi, i am newbie of socket. i want to ask some question. if i want to send file from client to server, how do i do? and if i want to send file from server to client, how do i do?
any pro help me and if possible, you can post code for an example
i need it very much
thank you for helping me:)... (1 Reply)
Discussion started by: tung1984
1 Replies
8. Programming
I want to send packets through single socket() but using two different port numbers in UDP. Anybody give some idea on this.
Thanks in advance.:) (2 Replies)
Discussion started by: naresh046
2 Replies
9. HP-UX
Hi,
How do I convet /dev/log from a pipe to a socket. As of now its is a pipe.
bash-4.0$ ls -l /dev/log
prw-rw-rw- 1 root sys 0 Jan 31 05:23 /dev/log
I need to have it as a socket.
Thanks (2 Replies)
Discussion started by: naan
2 Replies
10. UNIX for Advanced & Expert Users
Hai,
I am having one server/client both running in different host in UDP. How can i assure whether the data is recieved properly in client side. I am writing 250 KB in Server and client reading only 150 KB data. I am using select write in server and select read in client also.If i am putting one... (1 Reply)
Discussion started by: andrew.paul
1 Replies
LEARN ABOUT DEBIAN
checkbashisms
CHECKBASHISMS(1) General Commands Manual CHECKBASHISMS(1)
NAME
checkbashisms - check for bashisms in /bin/sh scripts
SYNOPSIS
checkbashisms script ...
checkbashisms --help|--version
DESCRIPTION
checkbashisms, based on one of the checks from the lintian system, performs basic checks on /bin/sh shell scripts for the possible presence
of bashisms. It takes the names of the shell scripts on the command line, and outputs warnings if possible bashisms are detected.
Note that the definition of a bashism in this context roughly equates to "a shell feature that is not required to be supported by POSIX";
this means that some issues flagged may be permitted under optional sections of POSIX, such as XSI or User Portability.
In cases where POSIX and Debian Policy disagree, checkbashisms by default allows extensions permitted by Policy but may also provide
options for stricter checking.
OPTIONS
--help, -h
Show a summary of options.
--newline, -n
Check for "echo -n" usage (non POSIX but required by Debian Policy 10.4.)
--posix, -p
Check for issues which are non POSIX but required to be supported by Debian Policy 10.4 (implies -n).
--force, -f
Force each script to be checked, even if it would normally not be (for instance, it has a bash or non POSIX shell shebang or appears
to be a shell wrapper).
--extra, -x
Highlight lines which, whilst they do not contain bashisms, may be useful in determining whether a particular issue is a false posi-
tive which may be ignored. For example, the use of "$BASH_ENV" may be preceded by checking whether "$BASH" is set.
--version, -v
Show version and copyright information.
EXIT VALUES
The exit value will be 0 if no possible bashisms or other problems were detected. Otherwise it will be the sum of the following error val-
ues:
1 A possible bashism was detected.
2 A file was skipped for some reason, for example, because it was unreadable or not found. The warning message will give details.
SEE ALSO
lintian(1).
AUTHOR
checkbashisms was originally written as a shell script by Yann Dirson <dirson@debian.org> and rewritten in Perl with many more features by
Julian Gilbey <jdg@debian.org>.
DEBIAN
Debian Utilities CHECKBASHISMS(1)