10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I have a static IP 188.8.131.52 and two computers which I wish to talk to each other. The two IPs are 184.108.40.206 and 220.127.116.11.
How do I do it. For example ls from one computer to the other.
TIA (8 Replies)
Discussion started by: Meow613
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
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. Red Hat
I am running JBOSS 6 ona RHEL5 server put it continuously crashes due to the number of CLOSE_WAIT connections on port 8080.
How can I kill the several hundred CLOSE_WAIT connections without killing the actual live "LISTENING" connection?
D. (2 Replies)
Discussion started by: Duffs22
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
6. UNIX for Advanced & Expert Users
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
7. UNIX for Dummies Questions & Answers
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
8. UNIX for Dummies Questions & Answers
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
9. UNIX for Dummies Questions & Answers
Can someone please explain the difference between a connection and a thread. Any explanation will help!
Thanks (3 Replies)
Discussion started by: suntan
10. UNIX for Advanced & Expert Users
In my organization in order for anyone to go to any Unix server they have to go through "SERVER A" and login as themselves.
Then people are free to go enywhere they please.
SERVER A, loggs in as himself
telnets to SERVER B, loggs in as guest
telnets to SERVER C, loggs in as... (8 Replies)
Discussion started by: jraitsev
IMAPPROXYD(8) IMAP proxy daemon IMAPPROXYD(8)
imapproxyd - IMAP proxy daemon
imapproxyd [ -f <config file name> ] [ -p <pidfile name> ]
This manual page documents briefly the imapproxyd command. This manual page was written for the Debian distribution because the original
program does not have a manual page.
UP-ImapProxy proxies IMAP transactions between an IMAP client and an IMAP server. The general idea is that the client should never know
that it is not talking to the real IMAP server, but ImapProxy caches server connections.
ImapProxy was written to compensate for webmail clients that are unable to maintain persistent connections to an IMAP server. Most webmail
clients need to log in to an IMAP server for nearly every single transaction; This behaviour can cause tragic performance problems on the
IMAP server. ImapProxy tries to deal with this problem by leaving server connections open for a short time after a webmail client logs
out. When the webmail client connects again, ImapProxy will determine if there is a cached connection available and reuse it if possible.
By default, UP-ImapProxy reads /etc/imapproxy.conf on startup. This can be changed by using the -f option
Unless foreground_mode has been enabled, UP-ImapProxy will write its PID to to a PID-file. It defaults to /var/run/imapproxy.pid, but can
be overridden with the -p option
This manual page was written by Jose Luis Tallon <email@example.com>, for the Debian GNU/Linux system (but may be used by others).
Dave McMurtrie Mar 12, 2004 IMAPPROXYD(8)