Re: "Resolve host names" does not resolve host names, posted by Stefan Ritt on Tue Aug 4 13:33:14 2015
|
In elog I simplu use the function gethostbyaddr() to resolve the host name. If this does not work, the underlying OS does not know the hostname either. Probably you can test this with "nslookup a.b.c.d", to see any further error message.
| Daniel Sajdyk wrote: |
|
Hello
I use Resolve host names = 1 in my config file, but I still get IP instead domain name.
I use elog in internal network with my own DNS.
Any sugesstions ?
Regards
Daniel.
|
|
|
Re: "Resolve host names" does not resolve host names, posted by Daniel Sajdyk on Tue Aug 18 14:23:29 2015
|
I'm sorry... it was my mistake. I put Resolve host names in logbook config instead global.
Regards Daniel.
| Stefan Ritt wrote: |
|
In elog I simplu use the function gethostbyaddr() to resolve the host name. If this does not work, the underlying OS does not know the hostname either. Probably you can test this with "nslookup a.b.c.d", to see any further error message.
| Daniel Sajdyk wrote: |
|
Hello
I use Resolve host names = 1 in my config file, but I still get IP instead domain name.
I use elog in internal network with my own DNS.
Any sugesstions ?
Regards
Daniel.
|
|
|
Insert TimeStamp not working, posted by Luca on Wed Jul 29 23:07:41 2015
|
Hi,
I have an eLog logbook installed on my machine.
If I click on the INSERT TIMESTAMP botton in this post a Timestamp of the kind "Wed Jul 29 23:09:15 2015" is added.
When I do the same (with the same browser) on my logbook, nothing is added. Ideas about what might be causing this?
Regards
Luca |
|
Re: Insert TimeStamp not working, posted by Stefan Ritt on Thu Jul 30 11:10:59 2015
|
That problem has been fixed this week by this commit: https://bitbucket.org/ritt/elog/commits/5a8547bd995d88d7e314de30ee4bce71aa129c00
Please upgrade to the current revision from the bitbucket repository and recompile elog.
| Luca wrote: |
|
Hi,
I have an eLog logbook installed on my machine.
If I click on the INSERT TIMESTAMP botton in this post a Timestamp of the kind "Wed Jul 29 23:09:15 2015" is added.
When I do the same (with the same browser) on my logbook, nothing is added. Ideas about what might be causing this?
Regards
Luca
|
|
Monitoring a logbook for changes, posted by Johan Forsberg on Tue Jan 12 15:06:42 2016
|
Hi again!
I've another need that you probably already thought of :)
I'd like to be able to efficiently monitor a logbook for changes (new or edited posts) somehow. The most reasonable way I've found so far is to periodically poll a search that looks for posts after the time of the last poll. But that might note be very efficient, especially if the polling period gets short (or number of clients grows).
Is there some other feature that could be used for this? I was thinking maybe the ETag or Last-Modified HTTP header field could be used to show changes to a logbook by just reading the headers, but it would also require HEAD request support which does not seem to be there.
Cheers,
Johan |
|
Re: Monitoring a logbook for changes, posted by Stefan Ritt on Tue Jan 12 16:10:34 2016
|
Use automatic email notifications or RSS feeds. Read the manual for that.
Stefan
| Johan Forsberg wrote: |
|
Hi again!
I've another need that you probably already thought of :)
I'd like to be able to efficiently monitor a logbook for changes (new or edited posts) somehow. The most reasonable way I've found so far is to periodically poll a search that looks for posts after the time of the last poll. But that might note be very efficient, especially if the polling period gets short (or number of clients grows).
Is there some other feature that could be used for this? I was thinking maybe the ETag or Last-Modified HTTP header field could be used to show changes to a logbook by just reading the headers, but it would also require HEAD request support which does not seem to be there.
Cheers,
Johan
|
|
|
Re: Monitoring a logbook for changes, posted by Tamas Gal on Wed Jan 13 08:37:42 2016
|
I recommend monitoring directly on the server. Here is an example of a very simply Python script (https://github.com/tamasgal/elog-slack) which monitors the files very efficiently and immediately pushes notifications to Slack (slack.com). Just look at the code, it's pretty straight forward and very easy to adapt it to other (web) services.
Btw. here is an ELOG entry of it https://midas.psi.ch/elogs/Forum/68224
| Johan Forsberg wrote: |
|
Hi again!
I've another need that you probably already thought of :)
I'd like to be able to efficiently monitor a logbook for changes (new or edited posts) somehow. The most reasonable way I've found so far is to periodically poll a search that looks for posts after the time of the last poll. But that might note be very efficient, especially if the polling period gets short (or number of clients grows).
Is there some other feature that could be used for this? I was thinking maybe the ETag or Last-Modified HTTP header field could be used to show changes to a logbook by just reading the headers, but it would also require HEAD request support which does not seem to be there.
Cheers,
Johan
|
|
|
Re: Monitoring a logbook for changes, posted by Johan Forsberg on Wed Jan 13 10:27:21 2016
|
Yeah, I found the RSS feed feature, but I could not get ETags/Last-Modified header fields which meant that I'd have to read and parse the entire feed every time. Maybe I made a mistake and they do work, but if not, I think it would make sense to implement as it should save work for both the server and the client.
| Johan Forsberg wrote: |
|
Hi again!
I've another need that you probably already thought of :)
I'd like to be able to efficiently monitor a logbook for changes (new or edited posts) somehow. The most reasonable way I've found so far is to periodically poll a search that looks for posts after the time of the last poll. But that might note be very efficient, especially if the polling period gets short (or number of clients grows).
Is there some other feature that could be used for this? I was thinking maybe the ETag or Last-Modified HTTP header field could be used to show changes to a logbook by just reading the headers, but it would also require HEAD request support which does not seem to be there.
Cheers,
Johan
|
|