Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 673 of 808  Not logged in ELOG logo
icon1.gif   User can modify Fixed Attributes Edit when selecting preview, posted by Allen on Thu May 7 15:09:09 2009 
Hi.  I'm pretty new to ELOG, so I'm not sure if I'm doing something wrong.
 
I have a bunch of fields set so that after an entry has been submitted, they cannot edit certain fields.  When I click the edit button, everything
icon8.gif   Embedded images break when moving from one book to another., posted by Mike on Fri May 8 16:32:03 2009 
Here's the issue. We use elog to develope products we need to be able to see all the thumbnail images in a
particular logbook. Our default view is to use the threaded view fully expanded in order to have all the thumbnails
be displayed for each product. This works fine but when we move one message to another logbook the thumbnails
icon8.gif   can't send form , posted by larbi benouahi on Thu May 14 14:26:36 2009 
Hi,
when i try to send a form after edit or create an entry i got this message : Connection closed by remote server
is there any idea
icon13.gif   E-log crash, posted by soren poulsen on Thu May 14 17:41:44 2009 
Hi
I am having a little problem with e-log that I can easily reproduce.
I have defined a number of constraints on my e-log fields and I am testing what happens when the user does not respect them.
    icon2.gif   Re: E-log crash, posted by Stefan Ritt on Thu May 14 17:59:04 2009 
 

    
        
            soren poulsen wrote:
        
        
            
    icon2.gif   Re: E-log crash, posted by soren poulsen on Tue May 19 15:19:16 2009 


    
        
            Stefan
Ritt wrote:
        
        
            
             
    icon2.gif   Re: elogd dies after receiving second SIGHUP, posted by Paul T. Keener on Wed Jun 3 19:53:13 2009 
> > elogd continues to run after a SIGHUP. If a second SIGHUP is received the daemon terminates.
> > This was observed on Solaris 10 (SPARC).
> > The documentation states that elogd should re-read configuration after receiving SIGHUP.
    icon2.gif   Re: elogd dies after receiving second SIGHUP, posted by Stefan Ritt on Thu Jun 4 09:49:13 2009 
> > > elogd continues to run after a SIGHUP. If a second SIGHUP is received the daemon terminates.
> > > This was observed on Solaris 10 (SPARC).
> > > The documentation states that elogd should re-read configuration after receiving SIGHUP.
ELOG V3.1.5-3fb85fa6