App-BCVI-NotifyClient
view release on metacpan or search on metacpan
lib/App/BCVI/NotifyClient.pm view on Meta::CPAN
}
sub _notify_handle_tty_monitoring {
my($self, @args) = @_;
my %opt = $self->_notify_get_options(@args) or return;
$opt{tty} ||= $self->_notify_current_tty;
if($opt{idle}) {
print "Starting background process to monitor $opt{tty} for $opt{idle} second idle period\n";
print "Kill monitor with: bnotify --kill\n";
$opt{output} = $default_poll_interval;
$self->_notify_fork_bg_tty_monitor(sub {
while(1) {
$self->_notify_wait_for_idle(\%opt);
$self->SUPER::send_command("terminal is idle");
$self->_notify_exit if $opt{once};
$self->_notify_wait_for_output(\%opt);
}
});
}
elsif($opt{output}) {
print "Starting background process to monitor $opt{tty} for output\n";
print "Kill monitor with: bnotify --kill\n";
$opt{idle} = $default_idle_time;
$self->_notify_fork_bg_tty_monitor(sub {
$self->_notify_wait_for_idle(\%opt);
while(1) {
$self->_notify_wait_for_output(\%opt);
$self->SUPER::send_command("output received");
$self->_notify_exit if $opt{once};
$self->_notify_wait_for_idle(\%opt);
}
lib/App/BCVI/NotifyClient.pm view on Meta::CPAN
die "No such file or device: $opt{tty}\n";
}
return %opt;
}
sub _notify_fork_bg_tty_monitor {
my($self, $monitor_sub) = @_;
fork() && exit; # Parent retuns to shell child continues in background
setsid();
# We have this code lying around - might as well abuse it
$self->App::BCVI::Server::save_pid();
$monitor_sub->();
exit; # Shouldn't be reached
}
lib/App/BCVI/NotifyClient.pm view on Meta::CPAN
=head1 NAME
App::BCVI::NotifyClient - Send a notification message back to the user's desktop
=head1 SYNOPSIS
Send a message to the desktop notifications widget on your workstation:
$ long-running-command; bnotify "long-running-command has finished"
or fork a background monitor to advise you when a subsequent command pauses for
input:
$ bnotify -i
Starting background process to monitor /dev/pts/0 for 5 second idle period
$ sudo apt-get dist-upgrade
...
=head1 DESCRIPTION
This module is a plugin for C<bcvi> (see: L<App::BCVI>). It uses the C<notify>
command to send a message back for display on the user's desktop. This plugin
assumes a plugin back on the workstation will route the message to the desktop
notification applet or use some other mechanism to bring it to the attention of
the user. The L<App::BCVI::NotifyDesktop> plugin is one implementation of the
lib/App/BCVI/NotifyClient.pm view on Meta::CPAN
alias bnotify="bcvi --no-path-xlate -c notify"
This alias might be used to signal the user that a long-running process has
completed on a remote server, for example:
pg_dump intranet >intranet.dump ; bnotify "Database dump is finished!"
=head1 OPTIONS
Instead of simply sending a message, you can provide options to fork a
background process which will send you a message later when something
interesting happens (or doesn't):
=over 4
=item B<< --idle [<seconds>] >> (alias -i)
If the specified number of seconds (default 20) elapse with no output being
written to the TTY, you will receive a notification that the TTY is idle. For
example you might use this option to fork a listener and then kick off a
dist-upgrade command. If the command pauses awaiting input then you will be
lib/App/BCVI/NotifyClient.pm view on Meta::CPAN
=item B<< --tty <path> >> (alias -t)
The C<--idle> and C<--output> options will monitor the current TTY by default.
This option allows you to monitor a different TTY or even a plain file.
=item B<< --once >> (alias -1)
The C<--idle> and C<--output> option will loop and notify you of each idle time
or output event. Use the C<<--once>> option if you only want to be told about
the first event. The background process will exit immediately after sending
the notification.
=item B<< --kill >> (alias -k)
Find and kill the background listener associated with the current TTY.
=back
=head1 SUPPORT
You can look for information at:
=over 4
=item * Source code
( run in 1.530 second using v1.01-cache-2.11-cpan-0d23b851a93 )