01-17-2005
I wouldn't put it in the DMZ, just open port 80 up to it and use someone like zoneedit to handle DNS for ya.
10 More Discussions You Might Find Interesting
1. UNIX Desktop Questions & Answers
Hello,
The system reboots in single user mode
what command to use to bring the system up regularly??
I get
INIT: cannot create /var/adm/utmpx
Type control -d to proceede with a normal startup
or give root passwd for system maintaince.
either way i don't have a change and ... (1 Reply)
Discussion started by: awk
1 Replies
2. UNIX for Dummies Questions & Answers
Hi all,
having read lots of posts about SU I don't quiet understand this :
I'm doing regular backups of my database (u betta do) and therefore use su - username -c "sqlscript special data_base" in a unixscript which is even using cron. (yep!)
Now I need some other script, still with this... (4 Replies)
Discussion started by: nulnul7
4 Replies
3. AIX
Hi,
we currently use a valisys licence :
it is based on a server (serv1)
it is reached only by one workstation (cam1)
In all licence files there is line with cam1 et serv1
We want to use cam22 (new workstation) instead of cam1
I made a copy the licences files with remplacing cam1 by cam22... (0 Replies)
Discussion started by: cadmanager
0 Replies
4. Solaris
I'm not sure where to post this but it's happening on a SunOS 5.8 server so I'll try here.
I've discovered some unexpected behavior when using tr.
For example:
echo a | tr
Z
echo b | tr
a
echo a | tr
B
echo a | tr
B
echo a | tr
A (8 Replies)
Discussion started by: Mike@Work
8 Replies
5. Shell Programming and Scripting
Hi folks,
there are windows device names in the sixth column of a comma separated file. A example device name is:
\\.\Tape0
I don't get the all string in to a variable, because of the preceding backslash. The first backslash is just cut off and my attempts to manipulate the string afterward... (0 Replies)
Discussion started by: wibo1
0 Replies
6. UNIX for Dummies Questions & Answers
What is the possible cause for the mount command to take ages? im trying to mount remotely : "mount -t nfs xx.x.x.x:/export/xyz/cdrom-4.0 /mnt/cdrom" on a system using bash. Im able to ping the remote server, but the system hangs or takes about half an hour to carry out this mount command.... (4 Replies)
Discussion started by: sahilb
4 Replies
7. UNIX for Dummies Questions & Answers
Hi there, I'm new to unix-environments.
I'm richard, and i'm mostly a web-developer, under php. I've done work in unix env before, but never had my own.
Today, I've got debian 3.1 r4 from the official site, and i've attempted to install it twice.
I installed it initially as "Desktop... (0 Replies)
Discussion started by: izua
0 Replies
8. UNIX for Dummies Questions & Answers
I am trying to figure awk.
I have a file in my home directory called testawk.sh, have made it executable, and have run it... But don't see any output.
This is the contents of the file:
#!/usr/bin/awk -f
{ print " - HI -" }I enter ./testawk.sh in the prompt, press enter, and watch as the... (2 Replies)
Discussion started by: matthewden
2 Replies
9. Programming
Hey, i am having a problem
First, i know java well and i have used C++ on occasion so i thought i would be able to deal with a class where they program in C. unfortunately i have hit some speed bumps that i am having problems.
Here is my problem:
I have a structure cache_t in the sample... (0 Replies)
Discussion started by: zephoid
0 Replies
10. UNIX and Linux Applications
I am having a bit of trouble plotting a histogram in gnuplot. I am trying to use it to draw bars side by side. The first bar is from column five in my data file. The second bar is actually three bars stacked on top of each other and should be as tall as the first bar. The data is from the 2nd,... (0 Replies)
Discussion started by: kingnothing
0 Replies
TALK(1) BSD General Commands Manual TALK(1)
NAME
talk -- talk to another user
SYNOPSIS
talk person [-x] [ttyname]
DESCRIPTION
Talk is a visual communication program which copies lines from your terminal to that of another user.
Options available:
person If you wish to talk to someone on your own machine, then person is just the person's login name. If you wish to talk to a user on
another host, then person is of the form 'user@host' ( or 'host.user' or 'host!user' or 'host:user' ).
-x If you wish to talk to a user who has dot character in username, the -x argument will force 'user@host' form of the person and talk
will take dots as part of user name.
ttyname If you wish to talk to a user who is logged in more than once, the ttyname argument may be used to indicate the appropriate terminal
name, where ttyname is of the form 'ttyXX' or 'pts/X'.
When first called, talk contacts the talk daemon on the other user's machine, which sends the message
Message from TalkDaemon@his_machine...
talk: connection requested by your_name@your_machine.
talk: respond with: talk your_name@your_machine
to that user. At this point, he then replies by typing
talk your_name@your_machine
It doesn't matter from which machine the recipient replies, as long as his login name is the same. Once communication is established, the
two parties may type simultaneously; their output will appear in separate windows. Typing control-L (^L) will cause the screen to be
reprinted. The erase, kill line, and word erase characters (normally ^H, ^U, and ^W respectively) will behave normally. To exit, just type
the interrupt character (normally ^C); talk then moves the cursor to the bottom of the screen and restores the terminal to its previous
state.
As of netkit-ntalk 0.15 talk supports scrollback; use esc-p and esc-n to scroll your window, and ctrl-p and ctrl-n to scroll the other win-
dow. These keys are now opposite from the way they were in 0.16; while this will probably be confusing at first, the rationale is that the
key combinations with escape are harder to type and should therefore be used to scroll one's own screen, since one needs to do that much less
often.
If you do not want to receive talk requests, you may block them using the mesg(1) command. By default, talk requests are normally not
blocked. Certain commands, in particular nroff(1), pine(1), and pr(1), may block messages temporarily in order to prevent messy output.
FILES
/etc/hosts to find the recipient's machine
/var/run/utmp to find the recipient's tty
SEE ALSO
mail(1), mesg(1), who(1), write(1), talkd(8)
BUGS
The protocol used to communicate with the talk daemon is braindead.
Also, the version of talk(1) released with 4.2BSD uses a different and even more braindead protocol that is completely incompatible. Some
vendor Unixes (particularly those from Sun) have been found to use this old protocol.
Old versions of talk may have trouble running on machines with more than one IP address, such as machines with dynamic SLIP or PPP connec-
tions. This problem is fixed as of netkit-ntalk 0.11, but may affect people you are trying to communicate with.
HISTORY
The talk command appeared in 4.2BSD.
Linux NetKit (0.17) November 24, 1999 Linux NetKit (0.17)