You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It cross mi mind to add some more functionalities based on the main context of your scripts:
Compatibility with terminal sessions
Let's say you have a terminal session opened even in you X environment, let's send a wall message to tty session with same content of the message sent with notify-send.
Reason? Because if you are out from your PC for few minutes you can lose an important info like "User is logged into your PC " so if it happens to have a terminal session opened that message will still be there.
Another good reason is that you can use the script not just for desktop but for servers to and when u are logged into a terminal session of your server you can react very fast if it's needed.
PID of Session
Adding the PID of the ssh session into the message body is very useful. If somehow you want to kill that new initiated ssh session, you can do it very fast if u have this info.
tail2notify as a service
Let's make it run as a service
tail2notify config file
Let's add it a configuration file support
tail2notify multiple instances
Add the possibility to configure multiple instances like one for ssh messages and another for vpn
What do you think ?
The text was updated successfully, but these errors were encountered:
Hi @stancufm
I'm still here on Github, but as you can see, I haven't touched this project since December 2011. Honestly I have zero inclination right now to work on it. I have a backlog of other projects that would take priority if I found some extra non-work free time for coding. Sorry!
It cross mi mind to add some more functionalities based on the main context of your scripts:
Compatibility with terminal sessions
Let's say you have a terminal session opened even in you X environment, let's send a wall message to tty session with same content of the message sent with notify-send.
Reason? Because if you are out from your PC for few minutes you can lose an important info like "User is logged into your PC " so if it happens to have a terminal session opened that message will still be there.
Another good reason is that you can use the script not just for desktop but for servers to and when u are logged into a terminal session of your server you can react very fast if it's needed.
PID of Session
Adding the PID of the ssh session into the message body is very useful. If somehow you want to kill that new initiated ssh session, you can do it very fast if u have this info.
tail2notify as a service
Let's make it run as a service
tail2notify config file
Let's add it a configuration file support
tail2notify multiple instances
Add the possibility to configure multiple instances like one for ssh messages and another for vpn
What do you think ?
The text was updated successfully, but these errors were encountered: