09-28-2005
Hi,
I can understand what you all mean, but I believe that MySQL has virtually no limits; so it would seem that any UNIX/Linux flavor hooked to MySQL should do pretty well also... yes? no?
What I'm curious about is what makes such an OS so special/expensive?
Is it more complex code, or more robust code, or just more code?
After all, code is code. It's just bits and bytes.
So what is the money actually buying for 65 G's ?
3 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I need to replace thousands of carriage returns/line breaks in a large xml file and with spaces. I hope to do so with a script, called, for example, "removeCRs." I would invoke this at the command line as
ml5003$ sed -f /Users/ml5003/removeCRs oldFile > newFile
The script, I presume, would... (4 Replies)
Discussion started by: ml5003
4 Replies
2. Shell Programming and Scripting
Hi, I would like to ask if someone could help me to shorten this process.
If example i will have a thousand files and i want to get there permisions. pls help.
$ sh researcher2.sh
rm /home/aris/logs/logna
rm a12
for i in `aclget /usr/bin/uname`
do
grep -e $i ownership | awk '{print $1}'... (13 Replies)
Discussion started by: invinzin21
13 Replies
3. UNIX for Dummies Questions & Answers
Hello,
I would like to concatenate several thousand files (~40,000) into 1. I cannot do it with cat *.extension - it gives me an error that there are too many arguments.
Any suggestions?
Thanks,
Gussi (6 Replies)
Discussion started by: Gussifinknottle
6 Replies
MESG(1) User Commands MESG(1)
NAME
mesg - display (or do not display) messages from other users
SYNOPSIS
mesg [option] [n|y]
DESCRIPTION
The mesg utility is invoked by a user to control write access others have to the terminal device associated with standard error output. If
write access is allowed, then programs such as talk(1) and write(1) may display messages on the terminal.
Traditionally, write access is allowed by default. However, as users become more conscious of various security risks, there is a trend to
remove write access by default, at least for the primary login shell. To make sure your ttys are set the way you want them to be set, mesg
should be executed in your login scripts.
ARGUMENTS
n Disallow messages.
y Allow messages to be displayed.
If no arguments are given, mesg shows the current message status on standard error output.
OPTIONS
-v, --verbose
Explain what is being done.
-V, --version
Display version information and exit.
-h, --help
Display help text and exit.
EXIT STATUS
The mesg utility exits with one of the following values:
0 Messages are allowed.
1 Messages are not allowed.
>1 An error has occurred.
FILES
/dev/[pt]ty[pq]?
SEE ALSO
login(1), talk(1), write(1), wall(1), xterm(1)
HISTORY
A mesg command appeared in Version 6 AT&T UNIX.
AVAILABILITY
The mesg command is part of the util-linux package and is available from https://www.kernel.org/pub/linux/utils/util-linux/.
util-linux July 2014 MESG(1)