09-14-2007
Quote:
Originally Posted by
Perderabo
Right this second, things seem ok. But even before the today's performance tweaks, there were periods where things semmed ok. So I will wait at least 1 full day before I respond to the poll. And then I will base my vote on the worst case I saw. I hope that this will result in a more useful data point. Or should I take the word "now" in the poll more literally?
Hi Perderabo!
Anyway you want to vote is OK with me! It's always much appreciated to get user feedback on things like performance and other service related topics.
8 More Discussions You Might Find Interesting
1. What is on Your Mind?
I have updated the backend hosting for UNIX.COM and would appreciate feedback either in the form of a vote in the poll or a post so that we can plan for more changes if any are needed.
In particular let me us know if you see any strange behavior from the site as there may still be some... (8 Replies)
Discussion started by: reborg
8 Replies
2. News, Links, Events and Announcements
About 4 years ago I wrote this tool inspired by Rob Urban's collect tool for DEC's Tru64 Unix. What makes this tool as different as collect was in its day is its ability to run at a low overhead and collect tons of stuff. I've expanded the general concept and even include data not available in... (0 Replies)
Discussion started by: MarkSeger
0 Replies
3. IP Networking
Setup a site to site VPN between two cisco routers.
One of the site locations is unable to access ports such as https://example.com:9001
How do I let them go into port 9001?
They can ssh, ftp, telnet and everything else.
Is this a VPN issue or ACL access issue?
I put
permit ip host... (0 Replies)
Discussion started by: photon
0 Replies
4. Web Development
Hi All,
I am currently managing a web site. I find that during the peak time period,ie,between 1300hrs to 2100hrs everyday,the response slows down whenever i access the applications hosted by the server.However when i try to access the static content in the web server,it loads quickly.
The... (2 Replies)
Discussion started by: Hari_Ganesh
2 Replies
5. IP Networking
Hi,
I am trying to establish vpn between my linux server and cisco asa at client side.
I installed openswan on my cent os.
Linux Server
eth0 - 182.2.29.10
Gateway - 182.2.29.1
eth1 - 192.9.200.75
I have simple IPtables Like
WAN="eth0"
LAN="eth1" (0 Replies)
Discussion started by: ashokvpp
0 Replies
6. IP Networking
Q: "Does Cisco 1921 router support,, act as an endpoint for, site to site VPNs using IPSec? If so, how many? "
A: If you get the Cisco 1921/k9 with the security services bundle then it will have built in security features. Cisco, typically includes IP Sec tunnels I believe as part of that... (0 Replies)
Discussion started by: Ayaerlee
0 Replies
7. IP Networking
Hi @all,
I try to connect 2 LANs with IPSec/Openswan
LAN 1: 192.168.0.0/24
LAN 2: 192.168.1.0/24
This is my Config:
conn HomeVPN # # Left security gateway, subnet behind it, nexthop toward right. left=192.168.1.29 ... (1 Reply)
Discussion started by: bahnhasser83
1 Replies
8. What is on Your Mind?
Hello, I am new here and my name is Robert. I was actually looking for a forums website where I can go with questions regarding Linux and embedded Linux applications. I am fairly new (6 months) to the world of Linux and embedded Linux applications and the the learning curve is steep. When I am not... (13 Replies)
Discussion started by: Circuits
13 Replies
talkd(8) System Manager's Manual talkd(8)
NAME
talkd, ntalkd - The remote communications server for the talk command
SYNOPSIS
talkd
ntalkd
DESCRIPTION
The talkd server notifies a user or callee when a client or caller wants to initiate a conversation. The talkd daemon sets up the conver-
sation if the callee accepts the invitation. The caller initiates a conversation by executing the talk command and specifying the callee.
The callee accepts the invitation by executing the talk command specifying the caller.
The talkd daemon listens at a socket for a LOOK_UP request from a local or remote talk client. On receiving a LOOK_UP request, talkd scans
its internal invitation table for an entry that pairs the client (the local or remote talk process) with a caller.
If an entry exists in the talkd daemon's international invitation table, the talkd daemon assumes that the client process is the callee.
The talkd daemon returns the appropriate rendezvous address to the talk process for the callee. The callee process then establishes a
stream connection with the caller process.
If an entry does not exist in the invitation table, the talkd daemon assumes that the client process is the caller. The talkd daemon then
receives the client process's ANNOUNCE request. When talkd receives the ANNOUNCE request, talkd broadcasts an invitation on the console of
the remote host where the callee is logged in, unless the caller specifies a particular tty. At approximately 1-minute intervals, talkd
rebroadcasts the invitation until either the invitation is answered by the callee or the call is canceled by the caller.
Debugging messages are sent to syslogd(8). For further information on the files used by this daemon, see the syslogd command.
FILES
Specifies the command path Defines Internet socket assignments Contains data about users who are currently logged in
NOTES
The Tru64 UNIX version of talkd uses the talk 4.3BSD protocol. This command is sometimes referred to as ntalkd. It is not compatible with
4.2BSD versions of talk.
RELATED INFORMATION
Commands: inetd(8), syslogd(8), talk(1) delim off
talkd(8)