ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
68235
|
Wed Jan 13 20:08:04 2016 |
| Johan Forsberg | johan.forsberg@maxlab.lu.se | Question | Linux | ELOG V3.1.0-241 | Re: Monitoring a logbook for changes |
Aha, that's interesting too! I'll have to look more carefully through the documentation... :)
Stefan Ritt wrote: |
You guys know that there is the possibility to execute an arbitrary script on each submission of a new messge? Just use "Execute new = <script>". In the script you have access to all parameters of the message. That's maybe simple than to watch the file set.
Tamas Gal wrote: |
I just noticed that there are multiple messages per file, so I have to adapt the parser. I'll update this thread when I'm done!
Johan Forsberg wrote: |
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 Gal wrote: |
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
|
|
|
|
|
|
73
|
Mon Jul 15 14:09:30 2002 |
| Joeri Mastop | joeri.mastop@knmi.nl | Bug report | | | Port specification with -p fails under RedHat Linux (2.0.4-1) |
Hello,
I noticed a strange behaviour with Elog 2.0.4 (i386 RPM) in Linux (RH 7.2).
I started Elog out-of-the-box with portnumber 888 ('sbin/elogd -p 888').
It runs just fine, but appears to listen to port 8080, the default! It
looks like the -p option on the command-line is ignored.
Anyone seen similar problems?
Joeri |
74
|
Mon Jul 15 15:05:22 2002 |
| Joeri Mastop | joeri.mastop@knmi.nl | Comment | | | Re: Port specification with -p fails (SOLVED, more or less) |
> Anyone seen similar problems?
Probably not if you read the config file, 'cause I didn't. Shame on me...
But what this shows (Stefan: correct me if I'm wrong) is that if you set
the port number in the [global] section of the config file, the command-line
option '-p' is ignored. FYI...
Joeri |
89
|
Sat Aug 3 17:35:39 2002 |
| Joe Nall | joe.nall@inet.com | Request | | | Re: Compiling elog 2.0.4 on Solaris |
> > > Comiling elogd 2.0.4 under Solaris obviously fails with
> > >
> > > gcc -o elog elog.c -lsocket -lnsl
> > > gcc -o elogd elogd.c -lsocket -lnsl
> > > elogd.c: In function `ss_file_find':
> > > elogd.c:1372: `alphasort' undeclared (first use in this function)
> > > elogd.c:1372: (Each undeclared identifier is reported only once
> > > elogd.c:1372: for each function it appears in.)
> > > make: *** [elogd] Error 1
> > >
> > > because alphasort is an ucb'ism which does not exist under SYSV
> > >
> > > ... not very portable :-(
> >
> > I was not aware of this. Actually, I don't need 'alphasort' so I removed
it
> > from the source. The update is at
> >
> > http://midas.psi.ch/cgi-bin/cvsweb/elog/elogd.c
> >
> > Please give it a try.
>
> ok - i just continued with 2.0.5, but apparently it still has an UCB'ism
> (scandir) that does not work under SYSV:
>
> $ make
> gcc -g -o elogd elogd.c -lsocket -lnsl
> Undefined first referenced
> symbol in file
> scandir /tmp/ccy0Z3iV.o
> ld: fatal: Symbol referencing errors. No output written to elogd
> collect2: ld returned 1 exit status
> make: *** [elogd] Error 1
> $ egrep scandir elogd.c
> n = scandir(path, &namelist, NULL, NULL);
> $
I am having the same experience with ELOG 2.0.5 and Solaris 8. Any work
around woud be appreciated. |
65726
|
Thu Feb 7 14:22:57 2008 |
| Jochen Krempel | krempel (at) ill.fr | Bug report | All | 2.7.2-2 | Absolut links for images in FCK Editor |
We use ELOG inside a local network, but we want to allow access also from outside the firewall.
The suggested solution from Elog Admin Guide worked fine until version ELOG V2.6.5-1844 (essentially without FCK Editor):
ssh -L 1234:your.server.name:8080 your.firewall.name firefox http://localhost:1234/
Howerver, since the update to ELOG V2.7.1-2002 the FCK Editor uses absolute links to insert images.
An image uploaded from the local network will have an address like:
http://your.server.name:8080/logbookname/080207_101110/Picture.jpg
while the same image uploaded through the firewall tunnel will have a link like:
http://localhost:1234/logbookname/080207_101110/Picture.jpg
Obviously images uploaded from outside are not visible from inside and vice versa.
Is it possible to convince FCK Editor to use relative links?
PS
ELOG is great!!
|
65739
|
Tue Feb 12 23:57:52 2008 |
| Jochen Krempel | krempel@ill.fr | Comment | All | 2.7.2-2 | Re: Absolut links for images in FCK Editor |
Stefan Ritt wrote: |
Jochen Krempel wrote: |
We use ELOG inside a local network, but we want to allow access also from outside the firewall.
The suggested solution from Elog Admin Guide worked fine until version ELOG V2.6.5-1844 (essentially without FCK Editor):
ssh -L 1234:your.server.name:8080 your.firewall.name firefox http://localhost:1234/
Howerver, since the update to ELOG V2.7.1-2002 the FCK Editor uses absolute links to insert images.
An image uploaded from the local network will have an address like:
http://your.server.name:8080/logbookname/080207_101110/Picture.jpg
while the same image uploaded through the firewall tunnel will have a link like:
http://localhost:1234/logbookname/080207_101110/Picture.jpg
Obviously images uploaded from outside are not visible from inside and vice versa.
Is it possible to convince FCK Editor to use relative links?
PS
ELOG is great!!
|
I fixed this in SVN revision #2038.
|
Thank you for the quick support! |
65850
|
Wed Apr 23 18:59:30 2008 |
| Jochen Krempel | krempel(at)ill.fr | Request | All | 2.7.3 | LaTeX support |
I would appreciate if elog could provide a simple support for mathematical expressions.
A solution similar to wikimedia should be easy to implement and would help a lot.
http://www.mediawiki.org/wiki/Manual:Running_MediaWiki_on_Windows#Alternative_Solution
The idea is to parse the elog entry for a tag (e.g. <math></math>), extract the code, wrap it into a latex file, and pass this to latex, GhostScript, and ImageMagic. (The latter are already used by Elog, therefore the changes should not be too big.) The resulting image file would then be referenced by the elog html code.
Of course, the FCKeditor would not support LaTeX. However, the majority of elog-useres should be scientists and rather familiar with LaTeX. Therefore it should be fine if the original LaTeX code is saved (e.g. in the ALT-tag of the image) and the replacement "code to image" is undone for editing.
Kind regards,
Jochen |
68264
|
Tue Feb 23 22:32:30 2016 |
| Jimmy Bria | jimmy.bria@gmail.com | Question | Linux | 3.0.0 | Re: Kerberos auth not available on 3.0 ? |
Hi Stefan - Do you know is Kerberos is available (compiled) on the Windows installer?
-Jimmy
Stefan Ritt wrote: |
Kerberos support is not compiled into the binary RPM. You have to comile from sources to get that. The reason is that there are different Kerberos libraries around, and different people need different ones.
/Stefan
|
|