elog (not elogd) submit does not work anymore, posted by Heiko Scheit on Fri Feb 13 12:21:25 2004
|
Somehow elog does not use the -s option (subdir) anymore,
resulting in a 'HTTP/1.1 404 Not Found' error.
For now I am using elog from version 2.3.9 together with elogd v2.5.0,
which seems to work OK. |
-W -Wall options (using gcc), posted by Heiko Scheit on Fri Feb 13 12:25:15 2004
|
Maybe consider using the options -W -Wall when compiling elogd.
There are several warning messages. |
Re: -W -Wall options (using gcc), posted by Heiko Scheit on Mon Feb 16 16:40:50 2004
|
> So I fixed all compiler generated warnigns except these:
>
> [midas@pc2075 ~/elog]$ gcc -g -O -W -Wall -o elogd src/elogd.c
> src/elogd.c: In function `set_cookie':
> src/elogd.c:4675: warning: `%y' yields only last 2 digits of year
> src/elogd.c: In function `send_file_direct':
> src/elogd.c:5483: warning: `%y' yields only last 2 digits of year
> src/elogd.c: In function `show_elog_list':
> src/elogd.c:11938: warning: `%x' yields only last 2 digits of year in some
> locales
> src/elogd.c:11957: warning: `%x' yields only last 2 digits of year in some
> locales
> src/elogd.c:11979: warning: `%x' yields only last 2 digits of year in some
> locales
> src/elogd.c:11987: warning: `%x' yields only last 2 digits of year in some
> locales
> src/elogd.c: In function `ctrlc_handler':
> src/elogd.c:15864: warning: empty body in an if-statement
> src/elogd.c: In function `hup_handler':
> src/elogd.c:15870: warning: empty body in an if-statement
>
> Do you know how to disable these warnings or any other workaround? I would
> like to compile without any remaining warnings.
Have a look at the gcc info pages:
$ info gcc "invoking gcc" "warning options" |
Re: -W -Wall options (using gcc), posted by Heiko Scheit on Mon Feb 16 17:18:39 2004
|
> > Have a look at the gcc info pages:
> >
> > $ info gcc "invoking gcc" "warning options"
>
> Sure, I'm not stupid!
Sorry, didn't mean to offend you.
> I looked for ~10 minutes how to turn off the remaining
> warnings, but I could not find it. The code is now correct, like I do want the
> "%y" format specifier in the strftime() function, but the warning is wrong.
One way to remove the warnings would be to use "%Y" in a separate strftime() call
and then taking only the last two digits (characters) of that string.
Something like:
old:
strftime(str, sizeof(str), "%A, %d-%b-%y %H:%M:%S GMT", gmt);
new:
strftime(str, sizeof(str), "%A, %d-%b-XX %H:%M:%S GMT", gmt);
strftime(year, sizeof(year), "%Y", gmt);
i=strstr(str,"XX"); /* find position of XX */
if ( i+1 < sizeof(str) ) {
str[i] =year[3];
str[i+1]=year[4];
} else ...
Somewhat cumbersome, but should work. Maybe consider using the four
digit year directly, where possible.
Gruss, Heiko |
elogd does not exit on SIGTERM, posted by Heiko Scheit on Wed Feb 18 16:54:27 2004
|
When trying to stop elogd processes with the kill command
elogd exits only after access to the logbook.
It should exit immediately, maybe after some cleanup. |
too many <table> tags, posted by Heiko Scheit on Mon Aug 2 14:56:56 2004
|
There are too many <table> tags when displaying a singel entry. E.g.
in http://midas.psi.ch/elogs/Config+Examples/1 the row 'Configuration Name'
is not aligned with the others (see attachment).
Looking at the HTML one sees that there are <table> tags for each row
which should not be there:
<tr><td><table width="100%" cellpadding=0 cellspacing=0><tr><td nowrap
class="attribname">Author:</td><td class="attribvalue">
Stefan Ritt </td>
</tr></table></td></tr> |
Re: too many <table> tags, posted by Heiko Scheit on Tue Aug 3 13:06:54 2004
|
> > There are too many <table> tags when displaying a singel entry. E.g.
> > in http://midas.psi.ch/elogs/Config+Examples/1 the row 'Configuration Name'
> > is not aligned with the others (see attachment).
>
> The <table> tags are there on purpose. As you can combine several attributes
> into one line (see this forum for example), it's necessary to make an
> independent <table> for each line.
Couldn't one include the extra <table> tag only when there is really more than
one attribute per line. All other lines could then be aligned properly.
To increase the width is not really a solution, since this depends on the
text size used. See attachment with really big text. |
curly parenthesis problem , posted by Heiko Scheit on Tue Aug 3 15:44:07 2004
|
Everything after curly parenthesis is ignored in attribute entry boxes
like 'Subject' above
What I typed in the subject line was exatcly this:
'curly parenthesis problem {abc}' |