with using wall command, how can i have a carriage return in my broadcast message. i try to broadcast from a file, i were to use "cat myfile | wall" for broadcasting. but when the message broadcast somehow the format run away.
this the text in my file:
Code:
line 1
line 2
line 3
when broadcast
Code:
line 1
l
ine 2
li
ne 3
Moderator's Comments:
edit by bakunin: please use CODE-tags for files contents too. This makes it stand out better. Thank you.
Under, Solaris 10 I have the following problem:
A script executed at command line runs with nice level 0, as expected.
Same script started under (user) crontab runs with nice level 2.
I would prefer it run at 0. Is this possible? If so, how?
Thanks. (0 Replies)
Hi I want to implement the nice command in the shell that I am building. I came to know that there is a corresponding nice() system call for the same. But since I will be forking different processes to run different commands typed on the command prompt, is there any way I can make a command... (2 Replies)
hello everybody:
I have some job running on tru64 system and Im the root, due to limited resources I end up with my job ( vdump) for example taking the lowest share, I researched the nice command on the net, but couldnt get enough info, can I use it to already running process or I only use it... (1 Reply)
OK... I'm fairly new to unix having the admin handed to me on a platter w/almost no training.
However, being a programmer, I do pick up things fairly easily, but this one is getting the best of me.
I have a unix server that runs multiple versions of the same ERP system, hand crafted for our... (1 Reply)
Hello,
Some guy said to me that using the nice command to decrease the priority of a process is a myth, that the operating system corrects the priorities as the processes need cpu. Is this true? (4 Replies)
Hello,
I am just starting with shell scripting, as everyone will soon see from my question. What I'm trying to do is call the Nice command to set the script process priority from /bin/ksh. The difference is I'm running it not directly through the shell, but through Bigfix (very similar to... (3 Replies)
Dear Friends,
I have a directory when i take du of that directory it takes alot of memory and cpu and I/O, i want to use nice to run my script that have du command slowly so it won't take I/O and cpu, please suggest. (6 Replies)
Hello Folks,
Recently our FreeBSD 7.1 i386 system became very sluggish.
Nothing much is happening over there & whatever is running takes eternity to complete.
All the troubleshooting hinted towards a very high nice percentage.
Can that be the culprit?
Pasting snippets of top command,... (7 Replies)
Discussion started by: vibhor_agarwali
7 Replies
LEARN ABOUT MINIX
wall
WALL(1) User Commands WALL(1)NAME
wall - write a message to all users
SYNOPSIS
wall [-n] [-t timeout] [-g group] [message | file]
DESCRIPTION
wall displays a message, or the contents of a file, or otherwise its standard input, on the terminals of all currently logged in users.
The command will wrap lines that are longer than 79 characters. Short lines are whitespace padded to have 79 characters. The command will
always put a carriage return and new line at the end of each line.
Only the superuser can write on the terminals of users who have chosen to deny messages or are using a program which automatically denies
messages.
Reading from a file is refused when the invoker is not superuser and the program is set-user-ID or set-group-ID.
OPTIONS -n, --nobanner
Suppress the banner.
-t, --timeout timeout
Abandon the write attempt to the terminals after timeout seconds. This timeout must be a positive integer. The default value is
300 seconds, which is a legacy from the time when people ran terminals over modem lines.
-g, --group group
Limit printing message to members of group defined as a group argument. The argument can be group name or GID.
-V, --version
Display version information and exit.
-h, --help
Display help text and exit.
NOTES
Some sessions, such as wdm, that have in the beginning of utmp(5) ut_type data a ':' character will not get the message from wall. This is
done to avoid write errors.
SEE ALSO mesg(1), talk(1), write(1), shutdown(8)HISTORY
A wall command appeared in Version 7 AT&T UNIX.
AVAILABILITY
The wall command is part of the util-linux package and is available from Linux Kernel Archive <https://www.kernel.org/pub/linux/utils/util-
linux/>.
util-linux August 2013 WALL(1)
08-13-2014
