Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 720 of 801  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Version Subject
  701   Wed Sep 15 00:16:19 2004        
I g
  707   Wed Sep 15 00:16:19 2004    QuestionWindows2.5.4-2Re: Use Email From not Working as Before...
I gave the user email address priority over the "Use email from" option, that
means only if the user does not have an email address, then the "Use email from"
value is used. Now I realize that the priority is maybe wrong, so I should give
the "use email from" switch the highest priority. Only if this flag is not
present, then the system uses the user's email address. If that one is not
present, too, then the system uses "elog@<host>".

I applied this change to the CVS version, so let me know if it is ok with you.
  700   Mon Sep 13 20:44:35 2004 Question Christopher Jonescjjones@zombieworld.comQuestionWindows2.5.4-2Use Email From not Working as Before...
Hi,

We just recently upgraded from an older version of Elog to the latest and
greatest, 2.5.4-2.  Everything is workinly nicely, except the "Use Email
From" option does not seem to work as before.  We have the option set so
that all e-mail that is sent should be from a single address, but instead it
just ignores that address and uses the e-mail address of the user currently
logged in.   

I have this set in the global section of the elogd.cfg:

Use Email From = elog@****.com

Please let me know if this is the intended function or if it may possible be
a bug.

Thanks,
Chris
  699   Thu Sep 9 21:40:47 2004 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.5.0Re: elogd does not exit on SIGTERM
> kill -HUP <pid>; sleep 2; kill <pid>

Thanks, I could reproduce the problem. It had to do that a SIGHUP aborts the select()
command, which some listen socket marked, so that elogd goes into an accept() call, waiting
there indefinitely (or until a new browser request arrives). I fixed that. New version
under CVS.
  698   Wed Sep 8 23:35:01 2004 Warning Heiko Scheith.scheit@mpi-hd.mpg.deBug fixLinux2.5.4Re: text display of ascii files not a good idea
> > [...]
> > > Probably it is fine to display only files ending in '.txt' per default.
> > > In addition a file that has more than say 1000 lines should probably 
> > > also not be displayed (as default, optional OK).  
> > 
> > No, '.txt' would definitely not be enough for me. I'm using elog to log all
> > administration of our network. In many cases, I simply attach a configuration
> > file. All those files are plain ASCII and none of them end in '.txt' - and I
> > would most definitely like them to be displayed inline like they are now. In
> > fact, this change was the main reason for me to upgrade to 2.5.4
> > 
> > Maybe a configuration option or a "display attachment" button would be the
> > best solution, then?
> > 
> > Cheerio,
> > 
> > Thomas
> 
> So to make everybody happy, it would probably be enough not to display inline any
> *.ps file, is that right? 

I think there should be size limit.  Imagine a multi MB text file (whatever it is;
elogd.c is already more than 1/2 MB and is likely to increase due to your
excellent support).  A client on an ISDN line would have to wait
several minutes and during this time elogd is busy and no other client can connect
(correct?).  Of course, if somebody really wants to see this file then there is
nothing to be done, but likely someone is flipping throught the messages using
to arrows on top to find the right entry....
So a configurable size limit seems appropriate, from which on 
only 'Display attachment' is displayed.  And/Or, for files
exceeding this limit, the first N (new config option) lines could be displayed.

But this should only influence ASCII files.  E.g. the behaviour for jpeg files
should not change, which is controlled by 'Hide default'.  Maybe a 'Display/Hide
defaut extension' option, where the extensions are listed that are to be displayed
is another idea, in addition to a 'Max Display ASCII inline size' option,
which can be set to zero to disable it altogether.

In any case, whatever you think is best.

Cheers, Heiko

> Is there any other ASCII format, which should not be
> displayed? PDF is binary, so it won't be displayed. What about long C files? Most
> people want to see them. In the recent version there is the "Hide attachment"
> link which can be clicked to not display an attachment inline. Mabe there should
> be a "Hide default = 0|1" config option...
  697   Wed Sep 8 23:03:36 2004 Reply Heiko Scheith.scheit@mpi-hd.mpg.deBug reportLinux2.5.0Re: elogd does not exit on SIGTERM
> > elogd does not exit if there is an 'unprocessed' HUP.  So when you do 
> > 
> > kill -HUP <pid>
> > kill <pid> 
> > 
> > elogd will only exit after it was accessed.
> 
> Can you please tell me how to reproduce this problem?
> 
> Even if I do a
> 
> kill -HUP <pid>; kill <pid>
> 
> it works immediately when I start elogd manually in interactive mode (not as daemon).

Even though I can't test this right now, I assume you have to wait a little
so that elogd jumps out of the 'select()' statement between the kill
commands.  Try: 

kill -HUP <pid>; sleep 2; kill <pid>

(I think the 'select()' timeout was 1 second.?)
  696   Wed Sep 8 17:39:43 2004 Agree Steve Jonessteve.jones@freescale.comBug reportAll2.5.4-2Re: URL bug in elogd.cfg
> This problem has been fixed in revision 1.462

Thank you!
  695   Wed Sep 8 17:38:54 2004 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.5.0Re: elogd does not exit on SIGTERM
> elogd does not exit if there is an 'unprocessed' HUP.  So when you do 
> 
> kill -HUP <pid>
> kill <pid> 
> 
> elogd will only exit after it was accessed.

Can you please tell me how to reproduce this problem?

Even if I do a

kill -HUP <pid>; kill <pid>

it works immediately when I start elogd manually in interactive mode (not as daemon).
ELOG V3.1.5-3fb85fa6