Re: Backtick in background does not exit when screen exits

Vincent Newell <[email protected]>
Newsgroups gmane.comp.gnu.screen.user
Message-ID <CAFMTCMb0kMU4vd--HF7RHSJOw0TCd0GaT0x=wD+4DnDJYr6D1w@mail.gmail.com>
(Argh, forsaken by Gmail, sorry.)  Continued:
I tried on both Ubuntu 14.04.4 updates version (Screen version 4.01.00devel
(GNU) 2-May-06)
as well as a fresh clone from master (Screen version 4.99.0 (build on Jul
29 2016 17:31:06)

I was able to reproduce this problem with the following lines in my
.screenrc
backtick 1 0 0 bash -ilc "while true ; do sleep 5 ; date ; done"
hardstatus alwayslastline "%1`"

Is there any way to make this backtick program exit on screen exit?

Thanks
Vince


On Fri, Jul 29, 2016 at 5:44 PM, Vincent Newell <[email protected]>
wrote:

> To whomever's listening -
>
> I am trying to create indicator to display a system state string.  This
> string comes from some software following a PUB-SUB architecture.  My first
> thought was to use backtick to callout periodically to 'poll' the state,
> but the act of initializing, subscribing, getting a message, and
> unsubscribing has a lot of overhead.  Since my software already supports
> PUB-SUB I was hoping backtick supports a background process.  And, just my
> luck!  It does!
>
> "If both the lifespan and the autorefresh parameters are zero, the
> backtick program is expected to stay in the background and generate output
> once in a while. In this case, the command is executed right away and
> screen stores the last line of output. If a new line gets printed screen
> will automatically refresh the hardstatus or the captions."
>
> However, it seems like the background command does not exit when screen
> exits.
>
> I tried on both Ubuntu 14.04.4 updates
>
>

_______________________________________________
screen-users mailing list
screen-users-mXXj517/[email protected]
https://lists.gnu.org/mailman/listinfo/screen-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.