Re: More than 100 attributes , posted by JD on Thu Jun 30 14:00:43 2016
|
Thank you Stefan, I think then I will leave it at the default value. I need a stable Systen
Stefan
Ritt wrote:
The limit is in the variable |
Re: More questions about groups, posted by Stefan Ritt on Thu Apr 21 22:54:46 2005
|
> I am running 2.5.8-3 with the elogd.c 1.632. I have attached the config
> file that I am using. I have a top group "src", with logbooks "SRC
> Analysis" and "SRC Mail" in it. These two logbooks share the same password
|
Re: More questions about groups, posted by Stephen A. Wood on Fri Apr 22 18:16:25 2005
|
> Thanks for reporting this bug. I fixed it in the current CVS version.
I get my Icons and Graphics in the top group now. Thanks for fixing it. |
Re: More adventures with SSL, posted by Stefan Ritt on Wed Jul 28 16:38:07 2010
|
Chuck Brost wrote:
Stefan, |
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 |
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. |
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. |
Re: Monitoring a logbook for changes, posted by Johan Forsberg on Wed Jan 13 10:29:54 2016
|
Yeah, I suppose something like that would be both faster and more efficient than polling ELOG itself. Fortunately the ELOG disk format looks easily parsed.
Thanks for the pointer!
Tamas |