kilianc / rtail

rtail(1) - Terminal output to the browser in seconds, using UNIX pipes.
http://rtail.org
1.62k stars 107 forks source link

daemonize programs #111

Open drakej opened 8 years ago

drakej commented 8 years ago

Just a nice to have but it would be much easier if there was a built in option or some sort of functionality to daemonize rtail-server. As is one has to build their own init scripts and scaffolding to support this.

Something similar to this would be nice for the client rtail program as well. Value added on that would be not just to daemonize the client, but provide it with a configuration file that tells it files to tail. This way one doesn't have to explicitly pipe every file socket to the process which doesn't scale well. I believe log.io had some of this functionality built in but as the README mentioned, it's no longer maintained and currently in a broken state.

kilianc commented 8 years ago

Thanks so much @drakej for stopping by and taking the time to share this, you made my day.

I agree with you this is necessary, and this is the kind of feedback that I am always looking for, real people's problems.

I'll think about what's the best way to "opinionate" deployment of rtail on a large scale real life app. Probably a rtail-manager with a nice conf file you can add to your version control?

drakej commented 8 years ago

Thanks for the quick response. I was actually able to create an init script around the rtail-server process on CentOS pretty easily. It's already working and appears stable but that was the easy part since I'm only targeting one process as a service on the distro I use. Getting that working on all platforms would be more work.

As far as the clients, that is the trickier one and an rtail-manager that lets you set up multiple STDIN sockets in a configuration file on a client node/server would be awesome. I saw the ticket about multitail but I'm not sure that's the best option. Primarily because it would aggregate all of the log files or input sources into one stream.

Looking forward to where this goes. I'll be watching :)

gkudelis commented 8 years ago

Hey! Just my two cents: I'm running both rtail-server and the client using supervisord. Makes it easy to manage/restart separate processes and keeps them alive in case something unexpected happens.

ghost commented 6 years ago

Spent several hours trying to get rtail working. The installation runs ok. I can start rtail-server manually. I can run commands in the terminal with the rtail command. But I am unable to access output from rtail-server on a web browser. If my web server homepage is at: http://localhost/ , what is the default access address for a running rtail server? Thanks!