Is there a wall log?Piping cat into wall (e.g. cat | wall)wall forces everyone to input something to get back to the prompt

Impossible Scrabble Words

Ethernet, Wifi and a little human psychology

Can I see Harvest moon in India?

Is "you will become a subject matter expert" code for "you'll be working on your own 100% of the time"?

In what sequence should an advanced civilization teach technology to medieval society to maximize rate of adoption?

What is this gigantic dish at Ben Gurion airport?

Wrong Schengen Visa exit stamp on my passport, who can I complain to?

Masking out non-linear shapes on canvas

What is the source of "You can achieve a lot with hate, but even more with love" (Shakespeare?)

Why is the car dealer insisting on a loan instead of cash?

Is there any reason to concentrate on the Thunderous Smite spell after using its effects?

What is the meaning of "order" in this quote?

How to draw a Venn diagram for X - (Y intersect Z)?

What does "boys rule, girls drool" mean?

What would happen if Protagoras v Euathlus were heard in court today?

Teleport everything in a large zone; or teleport all living things and make a lot of equipment disappear

Planar regular languages

Bash awk command with quotes

International Orange?

Insight into cavity resonators

Is the Dodge action perceptible to other characters?

Permutations in Disguise

Why is belonging not transitive?

Is it appropriate to CC a lot of people on an email



Is there a wall log?


Piping cat into wall (e.g. cat | wall)wall forces everyone to input something to get back to the prompt






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








2















A tool that runs day and night sometimes posts crucial information to the wall. Is there any way to redirect this output to a file for when I'm asleep? Alternatively, does wall keep a log of messages posted to it or is there a way to enable it?










share|improve this question
























  • Apparently, there are some implementations of wall that write to syslog: linux.die.net/man/1/wall

    – Arkadiusz Drabczyk
    7 hours ago











  • And the implementation is here I think: salsa.debian.org/debian/sysvinit/blob/master/src/wall.c

    – Arkadiusz Drabczyk
    6 hours ago











  • @Arkadiusz please do add that as an answer.

    – roaima
    6 hours ago











  • @roaima: ok, I did

    – Arkadiusz Drabczyk
    6 hours ago

















2















A tool that runs day and night sometimes posts crucial information to the wall. Is there any way to redirect this output to a file for when I'm asleep? Alternatively, does wall keep a log of messages posted to it or is there a way to enable it?










share|improve this question
























  • Apparently, there are some implementations of wall that write to syslog: linux.die.net/man/1/wall

    – Arkadiusz Drabczyk
    7 hours ago











  • And the implementation is here I think: salsa.debian.org/debian/sysvinit/blob/master/src/wall.c

    – Arkadiusz Drabczyk
    6 hours ago











  • @Arkadiusz please do add that as an answer.

    – roaima
    6 hours ago











  • @roaima: ok, I did

    – Arkadiusz Drabczyk
    6 hours ago













2












2








2








A tool that runs day and night sometimes posts crucial information to the wall. Is there any way to redirect this output to a file for when I'm asleep? Alternatively, does wall keep a log of messages posted to it or is there a way to enable it?










share|improve this question














A tool that runs day and night sometimes posts crucial information to the wall. Is there any way to redirect this output to a file for when I'm asleep? Alternatively, does wall keep a log of messages posted to it or is there a way to enable it?







wall






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked 8 hours ago









user75619user75619

1184 bronze badges




1184 bronze badges















  • Apparently, there are some implementations of wall that write to syslog: linux.die.net/man/1/wall

    – Arkadiusz Drabczyk
    7 hours ago











  • And the implementation is here I think: salsa.debian.org/debian/sysvinit/blob/master/src/wall.c

    – Arkadiusz Drabczyk
    6 hours ago











  • @Arkadiusz please do add that as an answer.

    – roaima
    6 hours ago











  • @roaima: ok, I did

    – Arkadiusz Drabczyk
    6 hours ago

















  • Apparently, there are some implementations of wall that write to syslog: linux.die.net/man/1/wall

    – Arkadiusz Drabczyk
    7 hours ago











  • And the implementation is here I think: salsa.debian.org/debian/sysvinit/blob/master/src/wall.c

    – Arkadiusz Drabczyk
    6 hours ago











  • @Arkadiusz please do add that as an answer.

    – roaima
    6 hours ago











  • @roaima: ok, I did

    – Arkadiusz Drabczyk
    6 hours ago
















Apparently, there are some implementations of wall that write to syslog: linux.die.net/man/1/wall

– Arkadiusz Drabczyk
7 hours ago





Apparently, there are some implementations of wall that write to syslog: linux.die.net/man/1/wall

– Arkadiusz Drabczyk
7 hours ago













And the implementation is here I think: salsa.debian.org/debian/sysvinit/blob/master/src/wall.c

– Arkadiusz Drabczyk
6 hours ago





And the implementation is here I think: salsa.debian.org/debian/sysvinit/blob/master/src/wall.c

– Arkadiusz Drabczyk
6 hours ago













@Arkadiusz please do add that as an answer.

– roaima
6 hours ago





@Arkadiusz please do add that as an answer.

– roaima
6 hours ago













@roaima: ok, I did

– Arkadiusz Drabczyk
6 hours ago





@roaima: ok, I did

– Arkadiusz Drabczyk
6 hours ago










2 Answers
2






active

oldest

votes


















2
















There are some implementations of wall that write to syslog, for
example http://salsa.debian.org/debian/sysvinit/blob/master/src/wall.c . In
its
manpage it
says:




For every invocation of wall a notification will be written to syslog,
with facility LOG_USER and level BR LOG_INFO




If you cannot control application's behavior or tell it to use logger
instead of wall you can create a wall wrapper that would run a
regular wall command and use logger to write to syslog. You can
either create this wrapper in a new directory, add it to your $PATH
and restart program that uses wall with new $PATH settings or,
especially if you cannot even restart the program, replace system-wide
wall for everyone if you have enough permissions to do so. In this
example I will show you how to do the latter. First, rename existing
wall program to wall.orig:



$ command -v wall
/usr/bin/wall
$ sudo mv /usr/bin/wall /usr/bin/wall.orig


The new /usr/bin/wall wrapper script could look like this:



#!/usr/bin/env sh

# wall wrapper - run wall commands with specified arguments and write
# a notification to syslog

wall.orig "$@"
logger "wall was ran with the following options: $*, result: $?"


Remember to make it executable:



sudo chmod +x /usr/bin/wall


Use it like a regular wall:



$ wall "test message"

Broadcast message from ja@comp (pts/14) (Sat Sep 14 22:34:43 2019):

test message


If you have a working logger and syslogd is running you should see
the following message log in one of the files in /var/log that
syslogd is routing the messages to:



Sep 14 22:34:43 comp ja: wall was ran with the following options: test message, result: 0


Of course, keep in mind that each time you will upgrade your system
using its built-in upgrade mechanisms it's possible that the original
/usr/bin/wall binary will be restored again.






share|improve this answer



























  • Cool stuff! Thanks.

    – user75619
    2 hours ago


















1
















There is a logging level that will write to all logged in users with wall



logger -p emerg 'The sky is falling in'


The logger with write messages to the appropriate file under /var/log. For emergency priority messages it will also send them to users with wall.






share|improve this answer



























  • It doesn't intercept messages posted to the wall though, does it? The tool that I mention, I don't control its behavior -- it always posts to the wall. The idea is to intercept these messages, write them to a file so that when I wake up I can examine it to see if anything happened during the night.

    – user75619
    5 hours ago













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/4.0/"u003ecc by-sa 4.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%2funix.stackexchange.com%2fquestions%2f541751%2fis-there-a-wall-log%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes









2
















There are some implementations of wall that write to syslog, for
example http://salsa.debian.org/debian/sysvinit/blob/master/src/wall.c . In
its
manpage it
says:




For every invocation of wall a notification will be written to syslog,
with facility LOG_USER and level BR LOG_INFO




If you cannot control application's behavior or tell it to use logger
instead of wall you can create a wall wrapper that would run a
regular wall command and use logger to write to syslog. You can
either create this wrapper in a new directory, add it to your $PATH
and restart program that uses wall with new $PATH settings or,
especially if you cannot even restart the program, replace system-wide
wall for everyone if you have enough permissions to do so. In this
example I will show you how to do the latter. First, rename existing
wall program to wall.orig:



$ command -v wall
/usr/bin/wall
$ sudo mv /usr/bin/wall /usr/bin/wall.orig


The new /usr/bin/wall wrapper script could look like this:



#!/usr/bin/env sh

# wall wrapper - run wall commands with specified arguments and write
# a notification to syslog

wall.orig "$@"
logger "wall was ran with the following options: $*, result: $?"


Remember to make it executable:



sudo chmod +x /usr/bin/wall


Use it like a regular wall:



$ wall "test message"

Broadcast message from ja@comp (pts/14) (Sat Sep 14 22:34:43 2019):

test message


If you have a working logger and syslogd is running you should see
the following message log in one of the files in /var/log that
syslogd is routing the messages to:



Sep 14 22:34:43 comp ja: wall was ran with the following options: test message, result: 0


Of course, keep in mind that each time you will upgrade your system
using its built-in upgrade mechanisms it's possible that the original
/usr/bin/wall binary will be restored again.






share|improve this answer



























  • Cool stuff! Thanks.

    – user75619
    2 hours ago















2
















There are some implementations of wall that write to syslog, for
example http://salsa.debian.org/debian/sysvinit/blob/master/src/wall.c . In
its
manpage it
says:




For every invocation of wall a notification will be written to syslog,
with facility LOG_USER and level BR LOG_INFO




If you cannot control application's behavior or tell it to use logger
instead of wall you can create a wall wrapper that would run a
regular wall command and use logger to write to syslog. You can
either create this wrapper in a new directory, add it to your $PATH
and restart program that uses wall with new $PATH settings or,
especially if you cannot even restart the program, replace system-wide
wall for everyone if you have enough permissions to do so. In this
example I will show you how to do the latter. First, rename existing
wall program to wall.orig:



$ command -v wall
/usr/bin/wall
$ sudo mv /usr/bin/wall /usr/bin/wall.orig


The new /usr/bin/wall wrapper script could look like this:



#!/usr/bin/env sh

# wall wrapper - run wall commands with specified arguments and write
# a notification to syslog

wall.orig "$@"
logger "wall was ran with the following options: $*, result: $?"


Remember to make it executable:



sudo chmod +x /usr/bin/wall


Use it like a regular wall:



$ wall "test message"

Broadcast message from ja@comp (pts/14) (Sat Sep 14 22:34:43 2019):

test message


If you have a working logger and syslogd is running you should see
the following message log in one of the files in /var/log that
syslogd is routing the messages to:



Sep 14 22:34:43 comp ja: wall was ran with the following options: test message, result: 0


Of course, keep in mind that each time you will upgrade your system
using its built-in upgrade mechanisms it's possible that the original
/usr/bin/wall binary will be restored again.






share|improve this answer



























  • Cool stuff! Thanks.

    – user75619
    2 hours ago













2














2










2









There are some implementations of wall that write to syslog, for
example http://salsa.debian.org/debian/sysvinit/blob/master/src/wall.c . In
its
manpage it
says:




For every invocation of wall a notification will be written to syslog,
with facility LOG_USER and level BR LOG_INFO




If you cannot control application's behavior or tell it to use logger
instead of wall you can create a wall wrapper that would run a
regular wall command and use logger to write to syslog. You can
either create this wrapper in a new directory, add it to your $PATH
and restart program that uses wall with new $PATH settings or,
especially if you cannot even restart the program, replace system-wide
wall for everyone if you have enough permissions to do so. In this
example I will show you how to do the latter. First, rename existing
wall program to wall.orig:



$ command -v wall
/usr/bin/wall
$ sudo mv /usr/bin/wall /usr/bin/wall.orig


The new /usr/bin/wall wrapper script could look like this:



#!/usr/bin/env sh

# wall wrapper - run wall commands with specified arguments and write
# a notification to syslog

wall.orig "$@"
logger "wall was ran with the following options: $*, result: $?"


Remember to make it executable:



sudo chmod +x /usr/bin/wall


Use it like a regular wall:



$ wall "test message"

Broadcast message from ja@comp (pts/14) (Sat Sep 14 22:34:43 2019):

test message


If you have a working logger and syslogd is running you should see
the following message log in one of the files in /var/log that
syslogd is routing the messages to:



Sep 14 22:34:43 comp ja: wall was ran with the following options: test message, result: 0


Of course, keep in mind that each time you will upgrade your system
using its built-in upgrade mechanisms it's possible that the original
/usr/bin/wall binary will be restored again.






share|improve this answer















There are some implementations of wall that write to syslog, for
example http://salsa.debian.org/debian/sysvinit/blob/master/src/wall.c . In
its
manpage it
says:




For every invocation of wall a notification will be written to syslog,
with facility LOG_USER and level BR LOG_INFO




If you cannot control application's behavior or tell it to use logger
instead of wall you can create a wall wrapper that would run a
regular wall command and use logger to write to syslog. You can
either create this wrapper in a new directory, add it to your $PATH
and restart program that uses wall with new $PATH settings or,
especially if you cannot even restart the program, replace system-wide
wall for everyone if you have enough permissions to do so. In this
example I will show you how to do the latter. First, rename existing
wall program to wall.orig:



$ command -v wall
/usr/bin/wall
$ sudo mv /usr/bin/wall /usr/bin/wall.orig


The new /usr/bin/wall wrapper script could look like this:



#!/usr/bin/env sh

# wall wrapper - run wall commands with specified arguments and write
# a notification to syslog

wall.orig "$@"
logger "wall was ran with the following options: $*, result: $?"


Remember to make it executable:



sudo chmod +x /usr/bin/wall


Use it like a regular wall:



$ wall "test message"

Broadcast message from ja@comp (pts/14) (Sat Sep 14 22:34:43 2019):

test message


If you have a working logger and syslogd is running you should see
the following message log in one of the files in /var/log that
syslogd is routing the messages to:



Sep 14 22:34:43 comp ja: wall was ran with the following options: test message, result: 0


Of course, keep in mind that each time you will upgrade your system
using its built-in upgrade mechanisms it's possible that the original
/usr/bin/wall binary will be restored again.







share|improve this answer














share|improve this answer



share|improve this answer








edited 2 hours ago

























answered 6 hours ago









Arkadiusz DrabczykArkadiusz Drabczyk

9,5683 gold badges20 silver badges36 bronze badges




9,5683 gold badges20 silver badges36 bronze badges















  • Cool stuff! Thanks.

    – user75619
    2 hours ago

















  • Cool stuff! Thanks.

    – user75619
    2 hours ago
















Cool stuff! Thanks.

– user75619
2 hours ago





Cool stuff! Thanks.

– user75619
2 hours ago













1
















There is a logging level that will write to all logged in users with wall



logger -p emerg 'The sky is falling in'


The logger with write messages to the appropriate file under /var/log. For emergency priority messages it will also send them to users with wall.






share|improve this answer



























  • It doesn't intercept messages posted to the wall though, does it? The tool that I mention, I don't control its behavior -- it always posts to the wall. The idea is to intercept these messages, write them to a file so that when I wake up I can examine it to see if anything happened during the night.

    – user75619
    5 hours ago















1
















There is a logging level that will write to all logged in users with wall



logger -p emerg 'The sky is falling in'


The logger with write messages to the appropriate file under /var/log. For emergency priority messages it will also send them to users with wall.






share|improve this answer



























  • It doesn't intercept messages posted to the wall though, does it? The tool that I mention, I don't control its behavior -- it always posts to the wall. The idea is to intercept these messages, write them to a file so that when I wake up I can examine it to see if anything happened during the night.

    – user75619
    5 hours ago













1














1










1









There is a logging level that will write to all logged in users with wall



logger -p emerg 'The sky is falling in'


The logger with write messages to the appropriate file under /var/log. For emergency priority messages it will also send them to users with wall.






share|improve this answer















There is a logging level that will write to all logged in users with wall



logger -p emerg 'The sky is falling in'


The logger with write messages to the appropriate file under /var/log. For emergency priority messages it will also send them to users with wall.







share|improve this answer














share|improve this answer



share|improve this answer








edited 4 hours ago









Arkadiusz Drabczyk

9,5683 gold badges20 silver badges36 bronze badges




9,5683 gold badges20 silver badges36 bronze badges










answered 7 hours ago









roaimaroaima

49.6k7 gold badges66 silver badges133 bronze badges




49.6k7 gold badges66 silver badges133 bronze badges















  • It doesn't intercept messages posted to the wall though, does it? The tool that I mention, I don't control its behavior -- it always posts to the wall. The idea is to intercept these messages, write them to a file so that when I wake up I can examine it to see if anything happened during the night.

    – user75619
    5 hours ago

















  • It doesn't intercept messages posted to the wall though, does it? The tool that I mention, I don't control its behavior -- it always posts to the wall. The idea is to intercept these messages, write them to a file so that when I wake up I can examine it to see if anything happened during the night.

    – user75619
    5 hours ago
















It doesn't intercept messages posted to the wall though, does it? The tool that I mention, I don't control its behavior -- it always posts to the wall. The idea is to intercept these messages, write them to a file so that when I wake up I can examine it to see if anything happened during the night.

– user75619
5 hours ago





It doesn't intercept messages posted to the wall though, does it? The tool that I mention, I don't control its behavior -- it always posts to the wall. The idea is to intercept these messages, write them to a file so that when I wake up I can examine it to see if anything happened during the night.

– user75619
5 hours ago


















draft saved

draft discarded















































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.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f541751%2fis-there-a-wall-log%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

Canceling a color specificationRandomly assigning color to Graphics3D objects?Default color for Filling in Mathematica 9Coloring specific elements of sets with a prime modified order in an array plotHow to pick a color differing significantly from the colors already in a given color list?Detection of the text colorColor numbers based on their valueCan color schemes for use with ColorData include opacity specification?My dynamic color schemes

Invision Community Contents History See also References External links Navigation menuProprietaryinvisioncommunity.comIPS Community ForumsIPS Community Forumsthis blog entry"License Changes, IP.Board 3.4, and the Future""Interview -- Matt Mecham of Ibforums""CEO Invision Power Board, Matt Mecham Is a Liar, Thief!"IPB License Explanation 1.3, 1.3.1, 2.0, and 2.1ArchivedSecurity Fixes, Updates And Enhancements For IPB 1.3.1Archived"New Demo Accounts - Invision Power Services"the original"New Default Skin"the original"Invision Power Board 3.0.0 and Applications Released"the original"Archived copy"the original"Perpetual licenses being done away with""Release Notes - Invision Power Services""Introducing: IPS Community Suite 4!"Invision Community Release Notes

199年 目錄 大件事 到箇年出世嗰人 到箇年死嗰人 節慶、風俗習慣 導覽選單