ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
67609
|
Wed Nov 13 14:41:07 2013 |
| David Pilgram | David.Pilgram@epost.org.uk | Question | Linux | 2.9.2-2475 | Re: date and time |
Hal Proctor wrote: |
> [13 Nov] > As my threads have lots of replies, I end up with a forest of ">" characters which makes it difficult to read > earlier quoted entries (what with word-wrapping of the browser). > I thought to replace the ">"s by a simple date entry prepended to the start of each reply. - much as I have > given at the top of this initial entry. > > So this is what I put in the config file: > > .... > Time format = %a %d %b %y > Date format = %d %b > Prepend on reply = [$date] \n > ... > > The time is used in the string for the Thread display. > > Only I don't get the date, with the date format, prepended to replies but the time, in the time format, as > > [Wed 13 Nov 13] > > Now this is hardly a disaster, but any ideas why the date formatting is being ignored?
https://midas.psi.ch/elogs/Forum/67405
Why all the > Characters? Maybe back off the version as stated in above link? Not sure about the date issue.
|
I don't know what happened here - I mean, I understand the ">" characters being added to the start of every line of a quoted previous entry, but now what then happened to the formatting.
By default in plain mode elog adds ">" to the start of every quoted line, just as quoting an email will do (some mailer programs).
If you're beyond your nteenth reply, word-wrapping of the browser etc makes past comments difficult to read. Of course it would be equally difficult in in html mode as the boxes would get more and more nested.
Not sure if your link here about html is relivent to the use of the ">" to indicate a quoted reply or not, although that wasn't really my question - which was about date format in the config file. |
67614
|
Thu Nov 14 11:19:12 2013 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Linux | 2.9.2-2475 | Re: date and time | > [13 Nov]
> As my threads have lots of replies, I end up with a forest of ">" characters which makes it difficult to read
> earlier quoted entries (what with word-wrapping of the browser).
> I thought to replace the ">"s by a simple date entry prepended to the start of each reply. - much as I have
> given at the top of this initial entry.
>
> So this is what I put in the config file:
>
> ....
> Time format = %a %d %b %y
> Date format = %d %b
> Prepend on reply = [$date] \n
> ...
>
> The time is used in the string for the Thread display.
>
> Only I don't get the date, with the date format, prepended to replies but the time, in the time format, as
>
> [Wed 13 Nov 13]
>
> Now this is hardly a disaster, but any ideas why the date formatting is being ignored?
Hi David,
yes, a $date is substituted with the "Time format" in the function build_subst_list().
I guess that is a bug, but it could break many existing logbooks to change it.
I leave this to Stefan.
There is a simple solution for your problem: you can execute a shell command.
Prepend on reply = $shell(date '+[%d %b]') \n
Reply string =
That snipped will do exactly what you want :-) (of course you need to have the "-x" option to start elogd.)
Kind Regards
Andreas |
67621
|
Fri Nov 15 13:43:18 2013 |
| David Pilgram | David.Pilgram@epost.org.uk | Question | Linux | 2.9.2-2475 | Re: date and time | > > [13 Nov]
> > As my threads have lots of replies, I end up with a forest of ">" characters which makes it difficult to read
> > earlier quoted entries (what with word-wrapping of the browser).
> > I thought to replace the ">"s by a simple date entry prepended to the start of each reply. - much as I have
> > given at the top of this initial entry.
> >
> > So this is what I put in the config file:
> >
> > ....
> > Time format = %a %d %b %y
> > Date format = %d %b
> > Prepend on reply = [$date] \n
> > ...
> >
> > The time is used in the string for the Thread display.
> >
> > Only I don't get the date, with the date format, prepended to replies but the time, in the time format, as
> >
> > [Wed 13 Nov 13]
> >
> > Now this is hardly a disaster, but any ideas why the date formatting is being ignored?
>
> Hi David,
> yes, a $date is substituted with the "Time format" in the function build_subst_list().
> I guess that is a bug, but it could break many existing logbooks to change it.
> I leave this to Stefan.
>
> There is a simple solution for your problem: you can execute a shell command.
>
> Prepend on reply = $shell(date '+[%d %b]') \n
> Reply string =
>
> That snipped will do exactly what you want :-) (of course you need to have the "-x" option to start elogd.)
>
> Kind Regards
> Andreas
Hi Andreas,
Thanks for this, I'll give the solution a go.
I take the point that if it's a bug, other logbooks may be affected if it were fixed; but perhaps another
parameter - $thedate or something could be created instead? |
68978
|
Mon May 20 16:39:50 2019 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | V3.1.4 | Re: custom subject for mail info | Use Email subject = $Subject
or a bit more detailed
Use Email subject = ELOG Ticket: "$Subject" posted by $Author
Daniel Pfuhl wrote: |
Hello,
we are extensively using ELOG for documenting changes in our infrastructure. It is very helpful for us.
To avoid multiple documentation efforts it would be even more helpful if the subject of an ELOG entry also could be the subject of the mail which is sent out. With that we could send mails to our ticket system and include the special ticket number to make the right assignment in our ticket system.
Does anyone know if this could be accomplished with the latest version of ELOG?
Best regards,
daniel
|
|
68979
|
Mon May 20 18:10:02 2019 |
| Daniel Pfuhl | daniel.pfuhl@medizin.uni-leipzig.de | Question | Windows | V3.1.4 | Re: custom subject for mail info | thank you!
Stefan Ritt wrote: |
Use Email subject = $Subject
or a bit more detailed
Use Email subject = ELOG Ticket: "$Subject" posted by $Author
Daniel Pfuhl wrote: |
Hello,
we are extensively using ELOG for documenting changes in our infrastructure. It is very helpful for us.
To avoid multiple documentation efforts it would be even more helpful if the subject of an ELOG entry also could be the subject of the mail which is sent out. With that we could send mails to our ticket system and include the special ticket number to make the right assignment in our ticket system.
Does anyone know if this could be accomplished with the latest version of ELOG?
Best regards,
daniel
|
|
|
69590
|
Fri Dec 2 14:44:46 2022 |
| Laurent Jean-Rigaud | lollspam@free.fr | Bug report | Linux | 3.14 EL7 EPEL | Re: custom css not loaded | Update : i tryed with last git, w/o ldap support and it seems the problem is solved with CCS URL on same machine (just replace the elogd binary from EPEL by new one just build w/o LDAP support and fallback on File to login for testing).
So my problem is the error during build with LDAP auth (since using C++) :-(
...
+ cd elog-3-14
+ make USE_SSL=1 USE_LDAP=1 USE_KRB5=1 'CFLAGS=-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -Wno-unused-result -Imxml'
c++ -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -Wno-unused-result -Imxml -DHAVE_SSL -DHAVE_KRB5 -DHAVE_LDAP -c -o mxml.o mxml/mxml.cxx
c++ -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -Wno-unused-result -Imxml -DHAVE_SSL -DHAVE_KRB5 -DHAVE_LDAP -w -c -o crypt.o src/crypt.cxx
c++ -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -Wno-unused-result -Imxml -DHAVE_SSL -DHAVE_KRB5 -DHAVE_LDAP -c -o strlcpy.o mxml/strlcpy.cxx
c++ -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -Wno-unused-result -Imxml -DHAVE_SSL -DHAVE_KRB5 -DHAVE_LDAP -o elog src/elog.cxx mxml.o crypt.o strlcpy.o -lssl -lkrb5 -lldap -llber
c++ -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -Wno-unused-result -Imxml -DHAVE_SSL -DHAVE_KRB5 -DHAVE_LDAP -w -c -o auth.o src/auth.cxx
src/auth.cxx: In function 'int auth_verify_password_ldap(LOGBOOK*, const char*, const char*, char*, int)':
src/auth.cxx:283:60: error: 'ldap_simple_bind_s' was not declared in this scope
bind = ldap_simple_bind_s(ldap_ld, ldap_bindDN, password);
^
src/auth.cxx:290:26: error: 'ldap_unbind' was not declared in this scope
ldap_unbind(ldap_ld);
^
src/auth.cxx:295:23: error: 'ldap_unbind' was not declared in this scope
ldap_unbind(ldap_ld);
^
src/auth.cxx: In function 'int ldap_adduser_file(LOGBOOK*, const char*, const char*, char*, int)':
src/auth.cxx:323:60: error: 'ldap_simple_bind_s' was not declared in this scope
bind = ldap_simple_bind_s(ldap_ld, ldap_bindDN, password);
^
src/auth.cxx:330:26: error: 'ldap_unbind' was not declared in this scope
ldap_unbind(ldap_ld);
^
src/auth.cxx:358:26: error: 'ldap_unbind' was not declared in this scope
ldap_unbind(ldap_ld);
^
src/auth.cxx:369:62: error: 'ldap_get_values' was not declared in this scope
if((values = ldap_get_values(ldap_ld,entry,attribute)) != NULL ) {
^
src/auth.cxx:378:35: error: 'ldap_value_free' was not declared in this scope
ldap_value_free(values);
^
src/auth.cxx:386:23: error: 'ldap_unbind' was not declared in this scope
ldap_unbind(ldap_ld);
^
src/auth.cxx: In function 'int auth_verify_password(LOGBOOK*, const char*, const char*, char*, int)':
src/auth.cxx:593:73: error: invalid conversion from 'const char*' to 'char*' [-fpermissive]
if (get_user_line(lbs, user, NULL, NULL, NULL, NULL, NULL, NULL) == 2) {
^
In file included from src/auth.cxx:30:0:
src/elogd.h:282:5: error: initializing argument 2 of 'int get_user_line(LOGBOOK*, char*, char*, char*, char*, BOOL*, time_t*, int*)' [-fpermissive]
int get_user_line(LOGBOOK * lbs, char *user, char *password, char *full_name, char *email,
^
make: *** [auth.o] Error 1
error: Bad exit status from /home/il/jeanrigaudl/rpmbuild/tmp/rpm-tmp.cKJL45 (%build)
Updated :
- from google (https://www.openldap.org/lists/openldap-technical/201104/msg00030.html), it seems it's necessary to add before "#include ldap.h" in src/auth.cxx
#define LDAP_DEPRECATED 1
- A cast must be added to src/auth.cxx:593 as already done somewhere with C++ commit :
if (get_user_line(lbs, (char *) user, NULL, NULL, NULL, NULL, NULL, NULL) == 2) {
-> elogd builds now with ldap :-) .
I installed elogd binary and i could login and the css url problem is gone.
Thanks to update auth.cxx (2 mods) and buildrpm (2 mods) in git (sorry, no pull request).
NB : PAM can not be activated under EL7 with same type of error. I disabled the feature as i do not use it.
+ cd elog-3-14
+ make USE_SSL=1 USE_PAM=1 'CFLAGS=-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -Wno-unused-result -Imxml'
c++ -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -Wno-unused-result -Imxml -DHAVE_SSL -DHAVE_PAM -c -o mxml.o mxml/mxml.cxx
c++ -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -Wno-unused-result -Imxml -DHAVE_SSL -DHAVE_PAM -w -c -o crypt.o src/crypt.cxx
c++ -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -Wno-unused-result -Imxml -DHAVE_SSL -DHAVE_PAM -c -o strlcpy.o mxml/strlcpy.cxx
c++ -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -Wno-unused-result -Imxml -DHAVE_SSL -DHAVE_PAM -o elog src/elog.cxx mxml.o crypt.o strlcpy.o -lssl -lpam -llber
c++ -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -Wno-unused-result -Imxml -DHAVE_SSL -DHAVE_PAM -w -c -o auth.o src/auth.cxx
src/auth.cxx: In function 'int elog_conv(int, const pam_message**, pam_response**, void*)':
src/auth.cxx:452:59: error: invalid conversion from 'void*' to 'pam_response*' [-fpermissive]
if((*resp = calloc(num_msg, sizeof(struct pam_response))) == NULL)
^
src/auth.cxx:457:33: error: invalid conversion from 'void*' to 'const char*' [-fpermissive]
if(!(resptok = strdup(my_data))) {
^
In file included from src/elogd.h:46:0,
from src/auth.cxx:30:
/usr/include/string.h:172:14: error: initializing argument 1 of 'char* strdup(const char*)' [-fpermissive]
extern char *strdup (const char *__s)
^
make: *** [auth.o] Error 1
error: Bad exit status from /home/il/jeanrigaudl/rpmbuild/tmp/rpm-tmp.V2LE4L (%build)
Laurent Jean-Rigaud wrote: |
Hi,
I use some CSS for each elog to resize column correcly and it seems that current ELOG version 3.14 available from EPEL for EL7 has a problem (maybe others also).
The browser console displays an error when loading ELOG logbook page (french locale ):
La feuille de style https:/xxxxx.xxx.xx/elog/MCO/1130_171749_REUNION_20221130_Q01.jpgelog-mco.css n’a pas été chargée car son type MIME, « text/html », n’est pas « text/css ».
It seems ELOG server send the css link with enclosure path (https:/xxxxx.xxx.xx/elog/MCO/1130_171749_REUNION_20221130_Q01.jpg) + css file (elog-mco.css) ?!?
I tryed to rebuild the last source from git under EL7 but it fails with LDAP libs (C++ regression already reported in elog:forum/69478). :-(
Thanks for help.
Laurent
|
|
651
|
Tue Aug 3 16:18:45 2004 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.5.4 | Re: curly parenthesis problem {smiley} | > 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}'
Just don't use curly brackets (;-)
Nevertheless I fixed it in the current version (see subject) |
67904
|
Thu May 14 02:19:53 2015 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Linux | 3.1 | Re: csv import timestamp | Hi Ferdinand,
and that is exactly what happens when you import a csv file with a date field:
the creation date ($entry time) of the imported entries will be used from the "Date" column in the file.
I've just tried it and it works like a charm. Did you have any problems doing it?
Cheers
Andreas
Ferdinand Gassauer wrote: |
I have to import a csv with a date field, which represents the creation date
this date should be used as "date" timestamp which is set automatically, otherwise all entries get the current datetime as timestamp
|
|
|