How do I opt out of recieving broadcast messages?
I am logged in to a university system and a very annoying n00b thinks he or she is some awesome hacker because she or he can broadcast an object dump to everyone using pipes. I bet they think it is funny because it looks like the matrix.
I was just wondering if there is a quick and easy way to opt out of recieving these messages from this user. Also what would be the command for all users (sometimes I would not want to recieve a message when I am in the depths of a difficult problem).
terminal
edited May 2 '11 at 7:26
Gilles
528k12810561583
asked May 2 '11 at 6:26
jones
347247
add a comment |
I am logged in to a university system and a very annoying n00b thinks he or she is some awesome hacker because she or he can broadcast an object dump to everyone using pipes. I bet they think it is funny because it looks like the matrix.
I was just wondering if there is a quick and easy way to opt out of recieving these messages from this user. Also what would be the command for all users (sometimes I would not want to recieve a message when I am in the depths of a difficult problem).
terminal
edited May 2 '11 at 7:26
Gilles
528k12810561583
asked May 2 '11 at 6:26
jones
347247
add a comment |
I am logged in to a university system and a very annoying n00b thinks he or she is some awesome hacker because she or he can broadcast an object dump to everyone using pipes. I bet they think it is funny because it looks like the matrix.
I was just wondering if there is a quick and easy way to opt out of recieving these messages from this user. Also what would be the command for all users (sometimes I would not want to recieve a message when I am in the depths of a difficult problem).
terminal
edited May 2 '11 at 7:26
Gilles
528k12810561583
asked May 2 '11 at 6:26
jones
347247
I am logged in to a university system and a very annoying n00b thinks he or she is some awesome hacker because she or he can broadcast an object dump to everyone using pipes. I bet they think it is funny because it looks like the matrix.
I was just wondering if there is a quick and easy way to opt out of recieving these messages from this user. Also what would be the command for all users (sometimes I would not want to recieve a message when I am in the depths of a difficult problem).
terminal
terminal
edited May 2 '11 at 7:26
Gilles
528k12810561583
asked May 2 '11 at 6:26
jones
347247
edited May 2 '11 at 7:26
Gilles
528k12810561583
asked May 2 '11 at 6:26
jones
347247
edited May 2 '11 at 7:26
Gilles
528k12810561583
edited May 2 '11 at 7:26
Gilles
528k12810561583
edited May 2 '11 at 7:26
Gilles
528k12810561583
528k12810561583
asked May 2 '11 at 6:26
jones
347247
asked May 2 '11 at 6:26
jones
347247
asked May 2 '11 at 6:26
jones
347247
347247
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
The command mesg n opts out of all messages. There is no way to prevent a specific user from sending you wall (Write ALL) message outside of removing execute permissions to the wall command for that user. The default permissions on my Ubuntu Linux computer allows for anyone to run wall and it will send messages to anyone who hasn't opted out with mesg n. Last note on this issue, just run mesg to see the current Opt-in/out status for receiving messages.
answered May 2 '11 at 6:41
penguin359
8,70423040
add a comment |
The first thing I would do would be to report this clown to the admins. Unfortunately there's no easy way for you to block him and only him.
The command to keep other users from writing messages on your terminal is mesg n. The mesg y command then allows writing again.
What this command does is to change the permissions of your terminal device file (e.g. /dev/tty0 or /dev/pts/8, etc.) to allow or disallow other users from writing to it. Typing who am i at the command prompt will often show you the name of your device, with the /dev/ prefix stripped off.
The traditional UNIX permission system allows you to set permissions separately for yourself, for a single user group, and for all other users. If you and everyone you want to talk to happen to be a member of a group that the h4x0r is not in, it's possible you could chgrp mygroup /dev/myterminal to set the file's group, then chmod 620 /dev/myterminal to set the permissions. (620 is shorthand for "user can read/write, group can write, all others have no permissions".)
Applying an access control list to your device file might be a way to do what you want, but that's system-dependent and non-standard, I've never done it, and it could cause problems for others if the login system isn't expecting it.
Finally, for more info (just in case you don't know already), try the man command -- man chmod, man chgrp, etc.
answered May 2 '11 at 7:09
Jander
11.5k43256
add a comment |
ls -l /usr/bin/wall
sudo chmod g+s /usr/bin/wall
echo foo | wall
mesg y
acb$ wall test
edited Feb 27 '13 at 13:16
Gilles
528k12810561583
answered Feb 27 '13 at 12:10
Sadiq Fazal
1
1
Your answer would be more helpful if it explained and motivated the given commands.
– N.N.
Feb 27 '13 at 13:29
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f12448%2fhow-do-i-opt-out-of-recieving-broadcast-messages%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
The command mesg n opts out of all messages. There is no way to prevent a specific user from sending you wall (Write ALL) message outside of removing execute permissions to the wall command for that user. The default permissions on my Ubuntu Linux computer allows for anyone to run wall and it will send messages to anyone who hasn't opted out with mesg n. Last note on this issue, just run mesg to see the current Opt-in/out status for receiving messages.
answered May 2 '11 at 6:41
penguin359
8,70423040
add a comment |
The command mesg n opts out of all messages. There is no way to prevent a specific user from sending you wall (Write ALL) message outside of removing execute permissions to the wall command for that user. The default permissions on my Ubuntu Linux computer allows for anyone to run wall and it will send messages to anyone who hasn't opted out with mesg n. Last note on this issue, just run mesg to see the current Opt-in/out status for receiving messages.
answered May 2 '11 at 6:41
penguin359
8,70423040
add a comment |
The command mesg n opts out of all messages. There is no way to prevent a specific user from sending you wall (Write ALL) message outside of removing execute permissions to the wall command for that user. The default permissions on my Ubuntu Linux computer allows for anyone to run wall and it will send messages to anyone who hasn't opted out with mesg n. Last note on this issue, just run mesg to see the current Opt-in/out status for receiving messages.
answered May 2 '11 at 6:41
penguin359
8,70423040
The command mesg n opts out of all messages. There is no way to prevent a specific user from sending you wall (Write ALL) message outside of removing execute permissions to the wall command for that user. The default permissions on my Ubuntu Linux computer allows for anyone to run wall and it will send messages to anyone who hasn't opted out with mesg n. Last note on this issue, just run mesg to see the current Opt-in/out status for receiving messages.
answered May 2 '11 at 6:41
penguin359
8,70423040
answered May 2 '11 at 6:41
penguin359
8,70423040
answered May 2 '11 at 6:41
penguin359
8,70423040
answered May 2 '11 at 6:41
penguin359
8,70423040
8,70423040
add a comment |
add a comment |
The first thing I would do would be to report this clown to the admins. Unfortunately there's no easy way for you to block him and only him.
The command to keep other users from writing messages on your terminal is mesg n. The mesg y command then allows writing again.
What this command does is to change the permissions of your terminal device file (e.g. /dev/tty0 or /dev/pts/8, etc.) to allow or disallow other users from writing to it. Typing who am i at the command prompt will often show you the name of your device, with the /dev/ prefix stripped off.
The traditional UNIX permission system allows you to set permissions separately for yourself, for a single user group, and for all other users. If you and everyone you want to talk to happen to be a member of a group that the h4x0r is not in, it's possible you could chgrp mygroup /dev/myterminal to set the file's group, then chmod 620 /dev/myterminal to set the permissions. (620 is shorthand for "user can read/write, group can write, all others have no permissions".)
Applying an access control list to your device file might be a way to do what you want, but that's system-dependent and non-standard, I've never done it, and it could cause problems for others if the login system isn't expecting it.
Finally, for more info (just in case you don't know already), try the man command -- man chmod, man chgrp, etc.
answered May 2 '11 at 7:09
Jander
11.5k43256
add a comment |
The first thing I would do would be to report this clown to the admins. Unfortunately there's no easy way for you to block him and only him.
The command to keep other users from writing messages on your terminal is mesg n. The mesg y command then allows writing again.
What this command does is to change the permissions of your terminal device file (e.g. /dev/tty0 or /dev/pts/8, etc.) to allow or disallow other users from writing to it. Typing who am i at the command prompt will often show you the name of your device, with the /dev/ prefix stripped off.
The traditional UNIX permission system allows you to set permissions separately for yourself, for a single user group, and for all other users. If you and everyone you want to talk to happen to be a member of a group that the h4x0r is not in, it's possible you could chgrp mygroup /dev/myterminal to set the file's group, then chmod 620 /dev/myterminal to set the permissions. (620 is shorthand for "user can read/write, group can write, all others have no permissions".)
Applying an access control list to your device file might be a way to do what you want, but that's system-dependent and non-standard, I've never done it, and it could cause problems for others if the login system isn't expecting it.
Finally, for more info (just in case you don't know already), try the man command -- man chmod, man chgrp, etc.
answered May 2 '11 at 7:09
Jander
11.5k43256
add a comment |
The first thing I would do would be to report this clown to the admins. Unfortunately there's no easy way for you to block him and only him.
The command to keep other users from writing messages on your terminal is mesg n. The mesg y command then allows writing again.
What this command does is to change the permissions of your terminal device file (e.g. /dev/tty0 or /dev/pts/8, etc.) to allow or disallow other users from writing to it. Typing who am i at the command prompt will often show you the name of your device, with the /dev/ prefix stripped off.
The traditional UNIX permission system allows you to set permissions separately for yourself, for a single user group, and for all other users. If you and everyone you want to talk to happen to be a member of a group that the h4x0r is not in, it's possible you could chgrp mygroup /dev/myterminal to set the file's group, then chmod 620 /dev/myterminal to set the permissions. (620 is shorthand for "user can read/write, group can write, all others have no permissions".)
Applying an access control list to your device file might be a way to do what you want, but that's system-dependent and non-standard, I've never done it, and it could cause problems for others if the login system isn't expecting it.
Finally, for more info (just in case you don't know already), try the man command -- man chmod, man chgrp, etc.
answered May 2 '11 at 7:09
Jander
11.5k43256
The first thing I would do would be to report this clown to the admins. Unfortunately there's no easy way for you to block him and only him.
The command to keep other users from writing messages on your terminal is mesg n. The mesg y command then allows writing again.
What this command does is to change the permissions of your terminal device file (e.g. /dev/tty0 or /dev/pts/8, etc.) to allow or disallow other users from writing to it. Typing who am i at the command prompt will often show you the name of your device, with the /dev/ prefix stripped off.
The traditional UNIX permission system allows you to set permissions separately for yourself, for a single user group, and for all other users. If you and everyone you want to talk to happen to be a member of a group that the h4x0r is not in, it's possible you could chgrp mygroup /dev/myterminal to set the file's group, then chmod 620 /dev/myterminal to set the permissions. (620 is shorthand for "user can read/write, group can write, all others have no permissions".)
Applying an access control list to your device file might be a way to do what you want, but that's system-dependent and non-standard, I've never done it, and it could cause problems for others if the login system isn't expecting it.
Finally, for more info (just in case you don't know already), try the man command -- man chmod, man chgrp, etc.
answered May 2 '11 at 7:09
Jander
11.5k43256
answered May 2 '11 at 7:09
Jander
11.5k43256
answered May 2 '11 at 7:09
Jander
11.5k43256
answered May 2 '11 at 7:09
Jander
11.5k43256
11.5k43256
add a comment |
add a comment |
ls -l /usr/bin/wall
sudo chmod g+s /usr/bin/wall
echo foo | wall
mesg y
acb$ wall test
edited Feb 27 '13 at 13:16
Gilles
528k12810561583
answered Feb 27 '13 at 12:10
Sadiq Fazal
1
1
Your answer would be more helpful if it explained and motivated the given commands.
– N.N.
Feb 27 '13 at 13:29
add a comment |
ls -l /usr/bin/wall
sudo chmod g+s /usr/bin/wall
echo foo | wall
mesg y
acb$ wall test
edited Feb 27 '13 at 13:16
Gilles
528k12810561583
answered Feb 27 '13 at 12:10
Sadiq Fazal
1
1
Your answer would be more helpful if it explained and motivated the given commands.
– N.N.
Feb 27 '13 at 13:29
add a comment |
ls -l /usr/bin/wall
sudo chmod g+s /usr/bin/wall
echo foo | wall
mesg y
acb$ wall test
edited Feb 27 '13 at 13:16
Gilles
528k12810561583
answered Feb 27 '13 at 12:10
Sadiq Fazal
1
ls -l /usr/bin/wall
sudo chmod g+s /usr/bin/wall
echo foo | wall
mesg y
acb$ wall test
edited Feb 27 '13 at 13:16
Gilles
528k12810561583
answered Feb 27 '13 at 12:10
Sadiq Fazal
1
edited Feb 27 '13 at 13:16
Gilles
528k12810561583
edited Feb 27 '13 at 13:16
Gilles
528k12810561583
edited Feb 27 '13 at 13:16
Gilles
528k12810561583
528k12810561583
answered Feb 27 '13 at 12:10
Sadiq Fazal
1
answered Feb 27 '13 at 12:10
Sadiq Fazal
1
answered Feb 27 '13 at 12:10
Sadiq Fazal
1
1
1
Your answer would be more helpful if it explained and motivated the given commands.
– N.N.
Feb 27 '13 at 13:29
add a comment |
1
Your answer would be more helpful if it explained and motivated the given commands.
– N.N.
Feb 27 '13 at 13:29
1
1
Your answer would be more helpful if it explained and motivated the given commands.
– N.N.
Feb 27 '13 at 13:29
Your answer would be more helpful if it explained and motivated the given commands.
– N.N.
Feb 27 '13 at 13:29
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f12448%2fhow-do-i-opt-out-of-recieving-broadcast-messages%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
