Only through style (that's what style is for, anyhow). 

Stefan Ritt wrote:

Kim Rosmo wrote: Hi :) First i have to say that i love this exelent program, and that it saved me Hours of trouble using it ^^ Thanks Stefan Ritt :)   Now.. here is my problem :P   1. I was wondering if there is a possibility to have separate 'Options Category'..  One for Admin and one for User?     If it is possible, can i have an example? This is unfortunately not possible. All users see the same options.  Kim Rosmo wrote: 2. How can i arrange pictures in the main window, f.eks 1 picture in center, to the right or wherever i want? You can put the pictures in a table, and align the table cells accordingly. Here is an example:   Now you can make the border invisible by setting "border=0". This however can only be done in the HTML mode, so you have to switch using the top left icon "Show HTML source code" and then manually edit the code. This requires some basic HTML knowledge. The result will look like this:

 Thanks for a fast reply :)

Its a lot of html tutorials on the net, so i think i will make it with the tables ^^

Regarding the 'Options Category' I can live with it... I have removed edit mode in User, so only Admin can delete or edit.

One last question.. Background color possible?  (Not Style)

Kim R

This is unfortunately not possible. All users see the same options. 

You can put the pictures in a table, and align the table cells accordingly. Here is an example:

Now you can make the border invisible by setting "border=0". This however can only be done in the HTML mode, so you have to switch using the top left icon "Show HTML source code" and then manually edit the code. This requires some basic HTML knowledge. The result will look like this:

Hi :)

First i have to say that i love this exelent program,

and that it saved me Hours of trouble using it ^^

Thanks Stefan Ritt :)

Now.. here is my problem :P

1. I was wondering if there is a possibility to have separate 'Options Category'..  One for Admin and one for User?

    If it is possible, can i have an example?

2. How can i arrange pictures in the main window, f.eks 1 picture in center, to the right or wherever i want?

Regards

Kim R

Hi Stefan,

> Just follow
> https://midas.psi.ch/elog/faq.html#19

That's what I attempted to do, but the need to restart ELOG before I could get to the gdb console prevented us from obtaining a stack trace.  I am now setting up a test ELOG server where we will continue 
trying to reproduce our crashes and obtain a stack trace.

> Crashes with attached images are getting reported more and more these days, but so far I was not able to reproduce it. Maybe it's related to ImageMagic 
> somehow, in which case disabling this feature might give some insight. To do so, you have to modify elogd.c and recompile. Change
> 
>    /* check for ImageMagick */
>    my_shell("convert -version", str, sizeof(str));
>    image_magick_exist = (strstr(str, "ImageMagick") != NULL);
> 
> 
> to
> 
>    /* check for ImageMagick */
>    image_magick_exist = 0;

This has now been done and installed on our production server.  I will let you know if we have any more crashes with ImageMagick disabled.

Many thanks,
Devin

> Hi, All.  Ever since upgrading from an old ELOG release on an aging windows machine to the latest version on Scientific Linux 4 (RHEL4), and 
> greatly increasing its use, we have seen frequent crashes of elogd.  This has become very disruptive to operations, and any help would be greatly 
> appreciated.  We are using Apache (running on the same machine as elogd) to secure ELOG using https as per the Administrator's Guide.

Just follow

https://midas.psi.ch/elog/faq.html#19

Crashes with attached images are getting reported more and more these days, but so far I was not able to reproduce it. Maybe it's related to ImageMagic 
somehow, in which case disabling this feature might give some insight. To do so, you have to modify elogd.c and recompile. Change

   /* check for ImageMagick */
   my_shell("convert -version", str, sizeof(str));
   image_magick_exist = (strstr(str, "ImageMagick") != NULL);


to

   /* check for ImageMagick */
   image_magick_exist = 0;

> ------
> 
> I plan on letting elogd create a core dump, but so far I haven't managed to change its cwd to a directory 
elog can write to.
> 
> Please let me know if there is any other information I can provide.  Any suggestions would be greatly 
appreciated.
> 
> Many thanks,
> Devin 

There are other debugers ...

  Whay don't you give them a try?

  example: Install "strace" (if you don't have it) and do something like ...

           strace   gdb /usr/local/sbin/elogd 6162  -debug 2>debug.out


   Also there is "ltrace", etc.

Hi, All.  Ever since upgrading from an old ELOG release on an aging windows machine to the latest version on Scientific Linux 4 (RHEL4), and 
greatly increasing its use, we have seen frequent crashes of elogd.  This has become very disruptive to operations, and any help would be greatly 
appreciated.  We are using Apache (running on the same machine as elogd) to secure ELOG using https as per the Administrator's Guide.

Anecdotally, the crashes seem to frequently happen when a user is attaching an image.  However, most of the time attachments succeed without 
incident.

I attempted to obtain a stack trace by attaching gdb to the process, but elogd died during the night.  It was urgently needed, so I needed to kill 
the elogd process (ptrace() kept it hanging around) and therefore could not obtain a stack trace.  For what it's worth, here is the output we do see in 
gdb:
------
[root@lnx248 ~]# gdb /usr/local/sbin/elogd 6162
GNU gdb Red Hat Linux (6.3.0.0-1.143.el4rh)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux-gnu"...(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".

Attaching to program: /usr/local/sbin/elogd, process 6162
Reading symbols from /lib/libssl.so.4...(no debugging symbols found)...done.
Loaded symbols for /lib/libssl.so.4
Reading symbols from /lib/tls/libc.so.6...(no debugging symbols found)...done.
Loaded symbols for /lib/tls/libc.so.6
Reading symbols from /usr/lib/libgssapi_krb5.so.2...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libgssapi_krb5.so.2
Reading symbols from /usr/lib/libkrb5.so.3...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libkrb5.so.3
Reading symbols from /lib/libcom_err.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/libcom_err.so.2
Reading symbols from /usr/lib/libk5crypto.so.3...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libk5crypto.so.3
Reading symbols from /lib/libresolv.so.2...
(no debugging symbols found)...done.
Loaded symbols for /lib/libresolv.so.2
Reading symbols from /lib/libcrypto.so.4...(no debugging symbols found)...done.
Loaded symbols for /lib/libcrypto.so.4
Reading symbols from /lib/libdl.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/libdl.so.2
Reading symbols from /usr/lib/libz.so.1...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libz.so.1
Reading symbols from /lib/ld-linux.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/ld-linux.so.2
Reading symbols from /lib/libnss_files.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/libnss_files.so.2
Reading symbols from /lib/libnss_nis.so.2...
(no debugging symbols found)...done.
Loaded symbols for /lib/libnss_nis.so.2
Reading symbols from /lib/libnsl.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib/libnsl.so.1
0x007ef7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
(gdb) c
Continuing.
Detaching after fork from child process 17720.
Detaching after fork from child process 17723.
Detaching after fork from child process 17726.
Detaching after fork from child process 17729.
Detaching after fork from child process 17732.
Detaching after fork from child process 17735.
Detaching after fork from child process 17738.
Detaching after fork from child process 17741.
Detaching after fork from child process 17744.
Detaching after fork from child process 17747.
Detaching after fork from child process 17750.
Detaching after fork from child process 17753.
Detaching after fork from child process 17756.
Detaching after fork from child process 17759.
Detaching after fork from child process 17762.
Detaching after fork from child process 17765.
Detaching after fork from child process 17768.
Detaching after fork from child process 17771.
Detaching after fork from child process 17774.
Detaching after fork from child process 17777.
Detaching after fork from child process 17780.
Detaching after fork from child process 17783.
Detaching after fork from child process 17786.
Detaching after fork from child process 17789.
Detaching after fork from child process 17792.
Detaching after fork from child process 17795.
Detaching after fork from child process 17798.
Detaching after fork from child process 17801.
Detaching after fork from child process 17807.
Detaching after fork from child process 17820.
Detaching after fork from child process 17823.
Detaching after fork from child process 17826.
Detaching after fork from child process 17829.
Detaching after fork from child process 17832.
Detaching after fork from child process 17835.
Detaching after fork from child process 17838.
Detaching after fork from child process 17841.
Detaching after fork from child process 17844.
Detaching after fork from child process 17847.
Detaching after fork from child process 17850.
Detaching after fork from child process 17853.
Detaching after fork from child process 17856.
Detaching after fork from child process 17859.
Detaching after fork from child process 17862.
Detaching after fork from child process 17865.
Detaching after fork from child process 17868.
Detaching after fork from child process 17871.
Detaching after fork from child process 25429.
Detaching after fork from child process 25432.
Detaching after fork from child process 25472.
Detaching after fork from child process 25475.
Detaching after fork from child process 25478.
Detaching after fork from child process 25481.
Detaching after fork from child process 25525.
Detaching after fork from child process 25528.
Detaching after fork from child process 25572.
Detaching after fork from child process 25575.
Detaching after fork from child process 25578.
Detaching after fork from child process 25581.
Detaching after fork from child process 32422.
Detaching after fork from child process 32425.
Detaching after fork from child process 32437.
Detaching after fork from child process 32440.
Detaching after fork from child process 32469.
Detaching after fork from child process 32472.
Detaching after fork from child process 32478.
---Type <return> to continue, or q <return> to quit---
Detaching after fork from child process 32481.
ptrace: No such process.
0x007ef7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
(gdb) bt
#0  0x007ef7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
Cannot access memory at address 0xbfe43894
------

I plan on letting elogd create a core dump, but so far I haven't managed to change its cwd to a directory elog can write to.

Please let me know if there is any other information I can provide.  Any suggestions would be greatly appreciated.

Many thanks,
Devin