So my best bet is going to be to put alias wall=/script/wall.sh in my /etc/bash.bashrc and any other allowed shell rc's where my /script/wall.sh does the things I want. and change any scripts like my /etc/apcupsd/apccontrol and change its WALL=wall to WALL=/script/wall.sh as well. I'll just have to go searching through /etc/ for files containing wall This will get most things I care about but it might skip messages that some users may broadcast should adding the "#!/bin/bash" as the first line to shell scripts cause the script to use the alias? On Mon, Oct 23, 2017 at 4:53 AM, Karel Zak <kzak@xxxxxxxxxx> wrote: > On Wed, Oct 18, 2017 at 02:06:25PM -0600, Jeff Sadowski wrote: >> I would like to know if this feature is built into wall or is there a >> good work around? > > wall is usually used by superuser. I guess if you can all "wall" than > you can also call for example logger to write to the system logs. I > don't see reason to merge functionally of these tools together. > >> I would like to configure wall to run a script after anything is posted to wall. > > Why? Maybe there is better way go get your goal. > >> I would also like to log all wall messages. I could easily do that >> with a script. > > yes, script(1) is the right way > > Karel > > > -- > Karel Zak <kzak@xxxxxxxxxx> > http://karelzak.blogspot.com -- To unsubscribe from this list: send the line "unsubscribe util-linux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
