Why is the output of wall command not displaying in stdout?












5















I am using ubuntu 14.04. I'm executing the wall command like this:



$ wall
Hi this is for testing
^d


But it doesn't display the message in terminal. I'm just executing the wall command in my machine; I'm not sending it to anyone. How could I solve this problem?



Snapshot for wall command



Thank You...










share|improve this question

























  • Test it in TTY . I had the same issue in 16.04 , where it doesn't display in GUI but does display in TTY. I suspect it may be a form of bug

    – Sergiy Kolodyazhnyy
    Jul 7 '16 at 10:04











  • But why its not working in GUI, My colleagues using the same version of Ubuntu 14.04. But in those machines it's working in GUI...

    – Ganapathy
    Jul 7 '16 at 10:33











  • Can you run it with strace so we see if it has any permissions issues perhaps? strace -e open wall should list numerous open(2) calls, and the last one should be something like open("/dev/pts/0", O_WRONLY|O_NONBLOCK|O_LARGEFILE) = ...

    – Josip Rodin
    Jul 9 '16 at 21:13











  • I tried it, but it doesn't show that path. Instead of that it gives like this, open("/var/run/utmp", O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 3 +++ exited with 0 +++

    – Ganapathy
    Jul 11 '16 at 5:21
















5















I am using ubuntu 14.04. I'm executing the wall command like this:



$ wall
Hi this is for testing
^d


But it doesn't display the message in terminal. I'm just executing the wall command in my machine; I'm not sending it to anyone. How could I solve this problem?



Snapshot for wall command



Thank You...










share|improve this question

























  • Test it in TTY . I had the same issue in 16.04 , where it doesn't display in GUI but does display in TTY. I suspect it may be a form of bug

    – Sergiy Kolodyazhnyy
    Jul 7 '16 at 10:04











  • But why its not working in GUI, My colleagues using the same version of Ubuntu 14.04. But in those machines it's working in GUI...

    – Ganapathy
    Jul 7 '16 at 10:33











  • Can you run it with strace so we see if it has any permissions issues perhaps? strace -e open wall should list numerous open(2) calls, and the last one should be something like open("/dev/pts/0", O_WRONLY|O_NONBLOCK|O_LARGEFILE) = ...

    – Josip Rodin
    Jul 9 '16 at 21:13











  • I tried it, but it doesn't show that path. Instead of that it gives like this, open("/var/run/utmp", O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 3 +++ exited with 0 +++

    – Ganapathy
    Jul 11 '16 at 5:21














5












5








5


1






I am using ubuntu 14.04. I'm executing the wall command like this:



$ wall
Hi this is for testing
^d


But it doesn't display the message in terminal. I'm just executing the wall command in my machine; I'm not sending it to anyone. How could I solve this problem?



Snapshot for wall command



Thank You...










share|improve this question
















I am using ubuntu 14.04. I'm executing the wall command like this:



$ wall
Hi this is for testing
^d


But it doesn't display the message in terminal. I'm just executing the wall command in my machine; I'm not sending it to anyone. How could I solve this problem?



Snapshot for wall command



Thank You...







command-line






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jul 7 '16 at 10:19









Zanna

50.6k13135241




50.6k13135241










asked Jul 7 '16 at 10:01









GanapathyGanapathy

1469




1469













  • Test it in TTY . I had the same issue in 16.04 , where it doesn't display in GUI but does display in TTY. I suspect it may be a form of bug

    – Sergiy Kolodyazhnyy
    Jul 7 '16 at 10:04











  • But why its not working in GUI, My colleagues using the same version of Ubuntu 14.04. But in those machines it's working in GUI...

    – Ganapathy
    Jul 7 '16 at 10:33











  • Can you run it with strace so we see if it has any permissions issues perhaps? strace -e open wall should list numerous open(2) calls, and the last one should be something like open("/dev/pts/0", O_WRONLY|O_NONBLOCK|O_LARGEFILE) = ...

    – Josip Rodin
    Jul 9 '16 at 21:13











  • I tried it, but it doesn't show that path. Instead of that it gives like this, open("/var/run/utmp", O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 3 +++ exited with 0 +++

    – Ganapathy
    Jul 11 '16 at 5:21



















  • Test it in TTY . I had the same issue in 16.04 , where it doesn't display in GUI but does display in TTY. I suspect it may be a form of bug

    – Sergiy Kolodyazhnyy
    Jul 7 '16 at 10:04











  • But why its not working in GUI, My colleagues using the same version of Ubuntu 14.04. But in those machines it's working in GUI...

    – Ganapathy
    Jul 7 '16 at 10:33











  • Can you run it with strace so we see if it has any permissions issues perhaps? strace -e open wall should list numerous open(2) calls, and the last one should be something like open("/dev/pts/0", O_WRONLY|O_NONBLOCK|O_LARGEFILE) = ...

    – Josip Rodin
    Jul 9 '16 at 21:13











  • I tried it, but it doesn't show that path. Instead of that it gives like this, open("/var/run/utmp", O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 3 +++ exited with 0 +++

    – Ganapathy
    Jul 11 '16 at 5:21

















Test it in TTY . I had the same issue in 16.04 , where it doesn't display in GUI but does display in TTY. I suspect it may be a form of bug

– Sergiy Kolodyazhnyy
Jul 7 '16 at 10:04





Test it in TTY . I had the same issue in 16.04 , where it doesn't display in GUI but does display in TTY. I suspect it may be a form of bug

– Sergiy Kolodyazhnyy
Jul 7 '16 at 10:04













But why its not working in GUI, My colleagues using the same version of Ubuntu 14.04. But in those machines it's working in GUI...

– Ganapathy
Jul 7 '16 at 10:33





But why its not working in GUI, My colleagues using the same version of Ubuntu 14.04. But in those machines it's working in GUI...

– Ganapathy
Jul 7 '16 at 10:33













Can you run it with strace so we see if it has any permissions issues perhaps? strace -e open wall should list numerous open(2) calls, and the last one should be something like open("/dev/pts/0", O_WRONLY|O_NONBLOCK|O_LARGEFILE) = ...

– Josip Rodin
Jul 9 '16 at 21:13





Can you run it with strace so we see if it has any permissions issues perhaps? strace -e open wall should list numerous open(2) calls, and the last one should be something like open("/dev/pts/0", O_WRONLY|O_NONBLOCK|O_LARGEFILE) = ...

– Josip Rodin
Jul 9 '16 at 21:13













I tried it, but it doesn't show that path. Instead of that it gives like this, open("/var/run/utmp", O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 3 +++ exited with 0 +++

– Ganapathy
Jul 11 '16 at 5:21





I tried it, but it doesn't show that path. Instead of that it gives like this, open("/var/run/utmp", O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 3 +++ exited with 0 +++

– Ganapathy
Jul 11 '16 at 5:21










1 Answer
1






active

oldest

votes


















1














Type the mesg command, and if it says "is n" (messages from wall are blocked), do mesg y. Of course, do man mesg;man wall first.






share|improve this answer



















  • 1





    I tested it, It gives 'y'. But the output is not displaying

    – Ganapathy
    Jul 8 '16 at 6:06











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f795908%2fwhy-is-the-output-of-wall-command-not-displaying-in-stdout%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









1














Type the mesg command, and if it says "is n" (messages from wall are blocked), do mesg y. Of course, do man mesg;man wall first.






share|improve this answer



















  • 1





    I tested it, It gives 'y'. But the output is not displaying

    – Ganapathy
    Jul 8 '16 at 6:06
















1














Type the mesg command, and if it says "is n" (messages from wall are blocked), do mesg y. Of course, do man mesg;man wall first.






share|improve this answer



















  • 1





    I tested it, It gives 'y'. But the output is not displaying

    – Ganapathy
    Jul 8 '16 at 6:06














1












1








1







Type the mesg command, and if it says "is n" (messages from wall are blocked), do mesg y. Of course, do man mesg;man wall first.






share|improve this answer













Type the mesg command, and if it says "is n" (messages from wall are blocked), do mesg y. Of course, do man mesg;man wall first.







share|improve this answer












share|improve this answer



share|improve this answer










answered Jul 7 '16 at 13:01









waltinatorwaltinator

22.2k74169




22.2k74169








  • 1





    I tested it, It gives 'y'. But the output is not displaying

    – Ganapathy
    Jul 8 '16 at 6:06














  • 1





    I tested it, It gives 'y'. But the output is not displaying

    – Ganapathy
    Jul 8 '16 at 6:06








1




1





I tested it, It gives 'y'. But the output is not displaying

– Ganapathy
Jul 8 '16 at 6:06





I tested it, It gives 'y'. But the output is not displaying

– Ganapathy
Jul 8 '16 at 6:06


















draft saved

draft discarded




















































Thanks for contributing an answer to Ask Ubuntu!


  • 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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f795908%2fwhy-is-the-output-of-wall-command-not-displaying-in-stdout%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

迪纳利

How did Captain America manage to do this?

南乌拉尔铁路局