ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 636 of 808

Not logged in

Find | Login | Help

Full | Summary | Threaded | Hide attachments

6457 Entries

Goto page Previous 1, 2, 3 ... 635, 636, 637 ... 806, 807, 808 Next

ID	Date	Author	Author Email	Category	OS	ELOG Version	Subject
1097	Mon Apr 18 09:04:21 2005	Stefan Ritt	stefan.ritt@psi.ch	Bug report	Windows	2.5.8-4	Re: Mail not sent but message says it has been sent
> If my email host refuses to send the email (476 connections denied), we > still get the message that the email has been sent - and no error message. > > How do I or can I send authentication information to the email server? This is not implemented right now, since the SMTP server at our institute does not use authentication, so I could not test it. If you give me access to a SMTP server with authentication, I could implement it.
1067	Sat Apr 9 06:07:42 2005	David Egolf	degolf@fujicolor.com	Question	Windows	2.5.8-3	Selective emails
I have a question about sending emails. I have a customer service ELog currently running but I would like to have an option to be able to pick from a list of people, one or more than one to send emails to with the logbook entry as the body. I am currently using the email option to send emails to a list if an emergency is used in a category but I would like to be able to send the entry to different people at different times. I would have everyone pre-entered with their names and emails and you could check a box by the person or people you want the log entry sent. I wasn't sure if this is possible with the current system. Thanks for any input. David Egolf PS. The emails are actually email enabled cell phones so the cs entries are going to drivers who pick up and drop off work for the company.
1069	Sat Apr 9 10:24:37 2005	Stefan Ritt	stefan.ritt@psi.ch	Question	Windows	2.5.8-3	Re: Selective emails
> I have a question about sending emails. I have a customer service ELog > currently running but I would like to have an option to be able to pick > from a list of people, one or more than one to send emails to with the > logbook entry as the body. I am currently using the email option to send > emails to a list if an emergency is used in a category but I would like to > be able to send the entry to different people at different times. I would > have everyone pre-entered with their names and emails and you could check > a box by the person or people you want the log entry sent. I wasn't sure > if this is possible with the current system. It is. Put an MOptions in you config file, and then put individual email statements there. Like Attributes = ..., Notify MOptions Notify = Joe, Jack, Jim Email Notify Joe = joe@fujicolor.com Email Notify Jack = jack@fujicolor.com Email Notify Jim = jim@fujicolor.com What this does it give you a checkbox for each name. If the check box is checked, then the corresponding email statement is executed. Note that the email address does not have to correspond to the "Notify" value. You could also use completely different names, like "MOptions Notify = Security, Police, Admin", and then put some email address from specific people there.
1077	Tue Apr 12 01:05:20 2005	G	levineg@med.govt.nz	Bug report	Other	2.5.8-3	XML password files, replication & FreeBSD
Ok this really is 2 questions. 1) I have been running ELOG on FreeBSD no problem for a year now, but this new version 2.5.8-x doesn't seem to wanna work, it compiles fine with a few warnings (see attached logs). But has issues with password files, now it shows message "Can't open passwords.pwd" for all my logbooks. It did convert the password files to xml format. I had a good hard look at file permissions and config file with no luck. So I went back a version and compiled 2.5.7-1 which works just fine with old password files. So something with XML & FreeBSD?... 2) Version 2.5.7-1 (maybe this has been fixed in 2.5.8?) When I run a ./elogd -C http://elog.blah.here:88 it clones the config file just fine, also seems to copy over all logbook entries. But once I look through them there's a fault with one of the fields it copies over, so entries never show up. It should be: ======================================== Date: Tue Mar 01 19:41:29 2005 In reply to: 24 Work done by: someuser Work done at (dd/mm/yy hh:mm): 1/03/05 3:30pm Downtime duration: 0 min Planned: Yes Reason: Normal work Attachment: Encoding: plain But once cloned it looks like this: ======================================== Date: Tue Mar 01 19:41:29 2005 In reply to: 24 Work done by: someuser Work done at (dd/mm/yy hh: m): 1/03/05 3:30pm Downtime duration: 0 min Planned: Yes Reason: Normal work Attachment: Encoding: plain For some reason it looses the "m" so line 4 instead of having "hh:mm" has "hh: m" Cheers, GL.
Attachment 1: compiling_ELOG_Errors_2.5.7-1.txt
===[root] /usr/local/elog #gmake gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -o elog src/elog.c gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -c -o regex.o src/regex.c src/regex.c: In function `regex_compile': src/regex.c:1193: warning: comparison between signed and unsigned src/regex.c:1208: warning: comparison between signed and unsigned src/regex.c:1301: warning: comparison between signed and unsigned src/regex.c:1326: warning: comparison between signed and unsigned src/regex.c:1340: warning: comparison between signed and unsigned src/regex.c:1350: warning: comparison between signed and unsigned src/regex.c:1362: warning: comparison between signed and unsigned src/regex.c:1368: warning: comparison between signed and unsigned src/regex.c:1376: warning: comparison between signed and unsigned src/regex.c:1612: warning: comparison between signed and unsigned src/regex.c:1630: warning: suggest explicit braces to avoid ambiguous `else' src/regex.c:1642: warning: comparison between signed and unsigned src/regex.c:1650: warning: suggest explicit braces to avoid ambiguous `else' src/regex.c:1686: warning: comparison between signed and unsigned src/regex.c:1702: warning: comparison between signed and unsigned src/regex.c:1730: warning: comparison between signed and unsigned src/regex.c:1817: warning: comparison between signed and unsigned src/regex.c:1930: warning: comparison between signed and unsigned src/regex.c:1936: warning: comparison between signed and unsigned src/regex.c:1941: warning: comparison between signed and unsigned src/regex.c:1945: warning: comparison between signed and unsigned src/regex.c:1949: warning: comparison between signed and unsigned src/regex.c:1953: warning: comparison between signed and unsigned src/regex.c:1957: warning: comparison between signed and unsigned src/regex.c:1961: warning: comparison between signed and unsigned src/regex.c:1979: warning: comparison between signed and unsigned src/regex.c:2027: warning: comparison between signed and unsigned src/regex.c:2031: warning: comparison between signed and unsigned src/regex.c: In function `compile_range': src/regex.c:2240: warning: comparison between signed and unsigned src/regex.c:2242: warning: signed and unsigned type in conditional expression src/regex.c:2242: warning: signed and unsigned type in conditional expression src/regex.c: In function `re_match_2': src/regex.c:3317: warning: comparison between signed and unsigned src/regex.c:3407: warning: comparison between signed and unsigned src/regex.c:3431: warning: comparison between signed and unsigned src/regex.c:3470: warning: empty body in an else-statement src/regex.c:3484: warning: comparison between signed and unsigned src/regex.c:3500: warning: comparison between signed and unsigned src/regex.c:3775: warning: comparison between signed and unsigned src/regex.c:3775: warning: unused variable `destination' src/regex.c:3922: warning: comparison between signed and unsigned src/regex.c:3922: warning: unused variable `destination' src/regex.c:3975: warning: comparison between signed and unsigned src/regex.c:3975: warning: unused variable `destination' src/regex.c:4081: warning: comparison between signed and unsigned src/regex.c:4114: warning: comparison between signed and unsigned src/regex.c:4114: warning: unused variable `destination' src/regex.c:4127: warning: comparison between signed and unsigned src/regex.c:4127: warning: unused variable `destination' src/regex.c:4295: warning: comparison between signed and unsigned src/regex.c: In function `regcomp': src/regex.c:4770: warning: signed and unsigned type in conditional expression src/regex.c: In function `regerror': src/regex.c:4890: warning: comparison between signed and unsigned src/regex.c: At top level: src/regex.c:4882: warning: unused parameter 'preg' In file included from src/regex.c:3838: src/regex.c: In function `re_match_2': src/regex.c:4599: warning: passing arg 1 of `bcmp_translate' discards qualifiers from pointer target type src/regex.c:4599: warning: passing arg 2 of `bcmp_translate' discards qualifiers from pointer target type gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -o elogd src/elogd.c regex.o gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -o elconv src/elconv.c
Attachment 2: compiling_ELOG_Errors_2.5.8.txt
===[root] /usr/local/elog-2.5.8 #gmake gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -o elog src/elog.c gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -c -o regex.o src/regex.c src/regex.c: In function `regex_compile': src/regex.c:1193: warning: comparison between signed and unsigned src/regex.c:1208: warning: comparison between signed and unsigned src/regex.c:1301: warning: comparison between signed and unsigned src/regex.c:1326: warning: comparison between signed and unsigned src/regex.c:1340: warning: comparison between signed and unsigned src/regex.c:1350: warning: comparison between signed and unsigned src/regex.c:1362: warning: comparison between signed and unsigned src/regex.c:1368: warning: comparison between signed and unsigned src/regex.c:1376: warning: comparison between signed and unsigned src/regex.c:1612: warning: comparison between signed and unsigned src/regex.c:1630: warning: suggest explicit braces to avoid ambiguous `else' src/regex.c:1642: warning: comparison between signed and unsigned src/regex.c:1650: warning: suggest explicit braces to avoid ambiguous `else' src/regex.c:1686: warning: comparison between signed and unsigned src/regex.c:1702: warning: comparison between signed and unsigned src/regex.c:1730: warning: comparison between signed and unsigned src/regex.c:1817: warning: comparison between signed and unsigned src/regex.c:1930: warning: comparison between signed and unsigned src/regex.c:1936: warning: comparison between signed and unsigned src/regex.c:1941: warning: comparison between signed and unsigned src/regex.c:1945: warning: comparison between signed and unsigned src/regex.c:1949: warning: comparison between signed and unsigned src/regex.c:1953: warning: comparison between signed and unsigned src/regex.c:1957: warning: comparison between signed and unsigned src/regex.c:1961: warning: comparison between signed and unsigned src/regex.c:1979: warning: comparison between signed and unsigned src/regex.c:2027: warning: comparison between signed and unsigned src/regex.c:2031: warning: comparison between signed and unsigned src/regex.c: In function `compile_range': src/regex.c:2240: warning: comparison between signed and unsigned src/regex.c:2242: warning: signed and unsigned type in conditional expression src/regex.c:2242: warning: signed and unsigned type in conditional expression src/regex.c: In function `re_match_2': src/regex.c:3317: warning: comparison between signed and unsigned src/regex.c:3407: warning: comparison between signed and unsigned src/regex.c:3431: warning: comparison between signed and unsigned src/regex.c:3470: warning: empty body in an else-statement src/regex.c:3484: warning: comparison between signed and unsigned src/regex.c:3500: warning: comparison between signed and unsigned src/regex.c:3775: warning: comparison between signed and unsigned src/regex.c:3775: warning: unused variable `destination' src/regex.c:3922: warning: comparison between signed and unsigned src/regex.c:3922: warning: unused variable `destination' src/regex.c:3975: warning: comparison between signed and unsigned src/regex.c:3975: warning: unused variable `destination' src/regex.c:4081: warning: comparison between signed and unsigned src/regex.c:4114: warning: comparison between signed and unsigned src/regex.c:4114: warning: unused variable `destination' src/regex.c:4127: warning: comparison between signed and unsigned src/regex.c:4127: warning: unused variable `destination' src/regex.c:4295: warning: comparison between signed and unsigned src/regex.c: In function `regcomp': src/regex.c:4770: warning: signed and unsigned type in conditional expression src/regex.c: In function `regerror': src/regex.c:4890: warning: comparison between signed and unsigned src/regex.c: At top level: src/regex.c:4882: warning: unused parameter 'preg' In file included from src/regex.c:3838: src/regex.c: In function `re_match_2': src/regex.c:4599: warning: passing arg 1 of `bcmp_translate' discards qualifiers from pointer target type src/regex.c:4599: warning: passing arg 2 of `bcmp_translate' discards qualifiers from pointer target type gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -DHAVE_STRLCPY -c -o mxml.o ../mxml/mxml.c gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -I../mxml -o elogd src/elogd.c regex.o mxml.o gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -o elconv src/elconv.c
1079	Tue Apr 12 09:30:51 2005	Stefan Ritt	stefan.ritt@psi.ch	Bug report	Other	2.5.8-3	Re: XML password files, replication & FreeBSD
> I have been running ELOG on FreeBSD no problem for a year now, > but this new version 2.5.8-x doesn't seem to wanna work, it compiles fine > with a few warnings (see attached logs). > But has issues with password files, now it shows message "Can't open > passwords.pwd" for all my logbooks. It did convert the password files to > xml format. I had a good hard look at file permissions and config file with > no luck. So I went back a version and compiled 2.5.7-1 which works just > fine with old password files. So something with XML & FreeBSD?... Hard to say. The simplest would be if I could debug this. > Version 2.5.7-1 (maybe this has been fixed in 2.5.8?) > When I run a ./elogd -C http://elog.blah.here:88 it clones the config file > just fine, also seems to copy over all logbook entries. > But once I look through them there's a fault with one of the fields it > copies over, so entries never show up. > > It should be: > ======================================== > Date: Tue Mar 01 19:41:29 2005 > In reply to: 24 > Work done by: someuser > Work done at (dd/mm/yy hh:mm): 1/03/05 3:30pm > Downtime duration: 0 min > Planned: Yes > Reason: Normal work > Attachment: > Encoding: plain > > But once cloned it looks like this: > ======================================== > Date: Tue Mar 01 19:41:29 2005 > In reply to: 24 > Work done by: someuser > Work done at (dd/mm/yy hh: m): 1/03/05 3:30pm > Downtime duration: 0 min > Planned: Yes > Reason: Normal work > Attachment: > Encoding: plain > > > For some reason it looses the "m" so line 4 instead of having > "hh:mm" has "hh: m" Your problem is that the attribute "Work done at (dd/mm/yy hh:mm)" which contains a ":". This character is not allowed in attributes. Unfortunately I did not document this (and even didn't know this until now... (;-) ). So you should use the new option Type Work done at = datetime this gives you at the entry mask fields for day/month/year/hour/minute to fill out, so you don't have to write it directly into the attribute. Another option would be to use Comment Work done at = Please enter as (dd/mm/yy hh:mm) which just displays a comment below the attribute in the entry mask. - Stefan
1081	Wed Apr 13 00:40:55 2005	G	levineg@med.govt.nz	Bug report	Other	2.5.8-3	Re: XML password files, replication & FreeBSD
> > I have been running ELOG on FreeBSD no problem for a year now, > > but this new version 2.5.8-x doesn't seem to wanna work, it compiles fine > > with a few warnings (see attached logs). > > But has issues with password files, now it shows message "Can't open > > passwords.pwd" for all my logbooks. It did convert the password files to > > xml format. I had a good hard look at file permissions and config file with > > no luck. So I went back a version and compiled 2.5.7-1 which works just > > fine with old password files. So something with XML & FreeBSD?... > > Hard to say. The simplest would be if I could debug this. Anything I could send you to help debug this? > > > Version 2.5.7-1 (maybe this has been fixed in 2.5.8?) > > When I run a ./elogd -C http://elog.blah.here:88 it clones the config file > > just fine, also seems to copy over all logbook entries. > > But once I look through them there's a fault with one of the fields it > > copies over, so entries never show up. > > > > It should be: > > ======================================== > > Date: Tue Mar 01 19:41:29 2005 > > In reply to: 24 > > Work done by: someuser > > Work done at (dd/mm/yy hh:mm): 1/03/05 3:30pm > > Downtime duration: 0 min > > Planned: Yes > > Reason: Normal work > > Attachment: > > Encoding: plain > > > > But once cloned it looks like this: > > ======================================== > > Date: Tue Mar 01 19:41:29 2005 > > In reply to: 24 > > Work done by: someuser > > Work done at (dd/mm/yy hh: m): 1/03/05 3:30pm > > Downtime duration: 0 min > > Planned: Yes > > Reason: Normal work > > Attachment: > > Encoding: plain > > > > > > For some reason it looses the "m" so line 4 instead of having > > "hh:mm" has "hh: m" > > Your problem is that the attribute "Work done at (dd/mm/yy hh:mm)" which > contains a ":". This character is not allowed in attributes. Unfortunately I did > not document this (and even didn't know this until now... (;-) ). So you should > use the new option > > Type Work done at = datetime > > this gives you at the entry mask fields for day/month/year/hour/minute to fill > out, so you don't have to write it directly into the attribute. Another option > would be to use > > Comment Work done at = Please enter as (dd/mm/yy hh:mm) > > which just displays a comment below the attribute in the entry mask. > > - Stefan Ok, i see, the problem for me now is that this attribute name has been in use for half a year or so by me. So now I have 100's of logbook entries with the old name in them, if I change it's name then all old logbook entries will show up with that field blank. I'm not sure if there's an easy way to change that attribute's name in 100's of entries in 10's of logbooks, because I wouldn't want to try doing that by hand.. Any ideas? (i'm no good at scripting something like that 4 sure) Thanks, G.
1082	Wed Apr 13 09:06:46 2005	Stefan Ritt	stefan.ritt@psi.ch	Bug report	Other	2.5.8-3	Re: XML password files, replication & FreeBSD
> Ok, i see, the problem for me now is that this attribute name has been in use for > half a year or so by me. So now I have 100's of logbook entries with the old name > in them, if I change it's name then all old logbook entries will show up with that > field blank. I'm not sure if there's an easy way to change that attribute's name in > 100's of entries in 10's of logbooks, because I wouldn't want to try doing that by > hand.. Any ideas? (i'm no good at scripting something like that 4 sure) find . -name "a.log" -exec perl -pi -e 's\|Work done at (dd/mm/yy hh:mm):\|Work done at:\|g' {} \; Looks a bit cryptic, but searches for all a.log files, and starts perl to replace all occurences of "Work done at (dd/mm/yy hh:mm)" with "Word done at:". Better try this first with a copy of your logbook. After you successfully changed that, you have to modify the attribute list in elogd.cfg accordingly, like Attirbutes = ..., Work done at, ... Please note that after each manual modification of the logbook files, you have to restart elogd.
1085	Thu Apr 14 15:07:18 2005	Michael Husbyn	michaelh@online.no	Question	Linux	2.5.8-3	Re: MIME encoding of mail?
> What you can try is to debug the communication between elogd and the SMTP > server. Just turn on logging via > > Logfile = log.txt > Logging level = 3 > > After sending email, you see the conversation in log.txt. Maybe this gives you > some hints. I run with loggin level = 6: 14-Apr-2005 14:50:16 [pc-0460] {ikt} Email from elog@..... to Michael.Husbyn@.....,, SMTP host smtp......: 14-Apr-2005 14:50:16 [pc-0460] {ikt} 220 backup...... ESMTP Sendmail 8.12.11/8.12.11; Thu, 14 Apr 2005 14:59:18 +0200 14-Apr-2005 14:50:16 [pc-0460] {ikt} 14-Apr-2005 14:50:16 [pc-0460] {ikt} HELO njord...... 14-Apr-2005 14:50:16 [pc-0460] {ikt} 250 backup...... Hello njord...... [10.138.224.221], pleased to meet you 14-Apr-2005 14:50:16 [pc-0460] {ikt} MAIL FROM: elog@..... 14-Apr-2005 14:50:16 [pc-0460] {ikt} 250 2.1.0 elog@........ Sender ok 14-Apr-2005 14:50:16 [pc-0460] {ikt} RCPT TO: <Michael.Husbyn@.....> 14-Apr-2005 14:50:16 [pc-0460] {ikt} 250 2.1.5 <Michael.Husbyn@.....>... Recipient ok 14-Apr-2005 14:50:16 [pc-0460] {ikt} DATA 14-Apr-2005 14:50:16 [pc-0460] {ikt} 354 Enter mail, end with "." on a line by itself 14-Apr-2005 14:50:16 [pc-0460] {ikt} To: Michael.Husbyn@....., 14-Apr-2005 14:50:16 [pc-0460] {ikt} From: elog@..... Subject: IKT sak (110): Testing �� 14-Apr-2005 14:50:16 [pc-0460] {ikt} X-Mailer: Elog, Version 2.5.8-3 14-Apr-2005 14:50:16 [pc-0460] {ikt} X-Elog-URL: http://njord......:8090/ikt/110 14-Apr-2005 14:50:16 [pc-0460] {ikt} X-Elog-submit-type: web\|elog 14-Apr-2005 14:50:16 [pc-0460] {ikt} Date: Thu, 14 Apr 2005 14:50:16 +0200 14-Apr-2005 14:50:16 [pc-0460] {ikt} Content-Type: TEXT/PLAIN; charset=US-ASCII 14-Apr-2005 14:50:16 [pc-0460] {ikt} . 14-Apr-2005 14:50:16 [pc-0460] {ikt} 250 2.0.0 j3ECxI8e003851 Message accepted for delivery 14-Apr-2005 14:50:16 [pc-0460] {ikt} QUIT 14-Apr-2005 14:50:16 [pc-0460] {ikt} 221 2.0.0 backup...... closing connection 14-Apr-2005 14:50:16 [pc-0460] {ikt} READ entry #110 -- Sorry for the late reply btw, I've removed some information in the log (server names) What I can see is that it sends with charset=US-ASCII, even if the characters are non-US. Only outlooks have problem with understanding if the subject is not mime encoded. Ideas? Best regards Michael Husbyn

Goto page Previous 1, 2, 3 ... 635, 636, 637 ... 806, 807, 808 Next

ELOG V3.1.5-3fb85fa6