comment on

Looking for advice on how to best accomplish this in 2020. The last node I could find mentioning polling files was from 2004.

Rationale: I have a log file I want to tail out to the browser via Mojolicious websockets. I have a rudimentary solution in place where an XHR request is sent on a 10 second interval to the server (client pull) which then goes and checks for updates a la qx(tail -n50 $file) ... basically.

Having seen how awesome websockets can be, I want to use a sever-push model instead. The websockets logic is already in place... I just need to know how best to approach the file polling. Something like d/inotify maybe? Or stat() wrapped in a while loop (yuck)?

Thoughts??

Tommy
A mistake can be valuable or costly, depending on how faithfully you pursue correction

In reply to Polling a file for changes - Best Practices? by Tommy

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Pathologically Eclectic Rubbish Lister
	PerlMonks