Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 48 of 806  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
icon4.gif   Bug? Password file location changed, posted by David Spindler on Thu Nov 2 18:02:44 2006 
I just tried to upgrade from 2.6.1-1633 to 2.6.2-1734. Whenever I tried to access the elog, it showed my password to be invalid. I tried this on 2 machines and same results. I did notice on the second one when I started it from a command prompt that it was creating a new empty password file in a different location.

I have a password file called pwd.txt. It resides in the main elog directory, in my case, c:\elog, along with the elgod.exe and elogd.cfg. Apparently, the new version looks for it in the logbooks directory. I adjusted my path to the file and it works fine.

I am reporting this as a bug because it is my guess that this is not an expected result. I would expect the old elogd.cfg file to work without altering in the newer version.

Thanks, keep up the great work, Stefan. You have a great program.
David Spindler
    icon2.gif   Re: Bug? Password file location changed, posted by David Spindler on Thu Nov 2 18:10:07 2006 

David Spindler wrote:
I just tried to upgrade from 2.6.1-1633 to 2.6.2-1734. Whenever I tried to access the elog, it showed my password to be invalid. I tried this on 2 machines and same results. I did notice on the second one when I started it from a command prompt that it was creating a new empty password file in a different location.

I have a password file called pwd.txt. It resides in the main elog directory, in my case, c:\elog, along with the elgod.exe and elogd.cfg. Apparently, the new version looks for it in the logbooks directory. I adjusted my path to the file and it works fine.

I am reporting this as a bug because it is my guess that this is not an expected result. I would expect the old elogd.cfg file to work without altering in the newer version.

Thanks, keep up the great work, Stefan. You have a great program.
David Spindler

I also just noticed that the text files I use for presetting the text window also have to be in the logbooks directory.
    icon2.gif   Re: Conditional Email Notification by a text file, posted by Steve Jones on Thu Nov 2 23:16:11 2006 

An Thai wrote:
Hello,

I try to email by using a email text file to reduce the admin work.
  • MOptions Team = EUROPE, ASIA, AFRICA, AMERICA
  • Email Team EUROPE = $shell(type C:\EuropeEmailList.txt)

but i get always Email sent to Shell execution not enabled via -x flag

Is this feature not supported by ELOG or did i use the wrong syntax?

Thank you in advance.




Quote:
You need to start elogd with the "-x" flag
    icon2.gif   Re: Bug? Password file location changed, posted by Steve Jones on Thu Nov 2 23:17:10 2006 

David Spindler wrote:

David Spindler wrote:
I just tried to upgrade from 2.6.1-1633 to 2.6.2-1734. Whenever I tried to access the elog, it showed my password to be invalid. I tried this on 2 machines and same results. I did notice on the second one when I started it from a command prompt that it was creating a new empty password file in a different location.

I have a password file called pwd.txt. It resides in the main elog directory, in my case, c:\elog, along with the elgod.exe and elogd.cfg. Apparently, the new version looks for it in the logbooks directory. I adjusted my path to the file and it works fine.

I am reporting this as a bug because it is my guess that this is not an expected result. I would expect the old elogd.cfg file to work without altering in the newer version.

Thanks, keep up the great work, Stefan. You have a great program.
David Spindler

I also just noticed that the text files I use for presetting the text window also have to be in the logbooks directory.



Quote:
The relocation was a documented change that Stefan made intentionally. Yes, it caught me too Smile
    icon2.gif   Re: Conditional Email Notification by a text file, posted by An Thai on Fri Nov 3 01:03:33 2006 

Steve Jones wrote:

An Thai wrote:
Hello,

I try to email by using a email text file to reduce the admin work.
  • MOptions Team = EUROPE, ASIA, AFRICA, AMERICA
  • Email Team EUROPE = $shell(type C:\EuropeEmailList.txt)

but i get always Email sent to Shell execution not enabled via -x flag

Is this feature not supported by ELOG or did i use the wrong syntax?

Thank you in advance.




Quote:
You need to start elogd with the "-x" flag


Yes, i did it. But the problem is still there.
I exactly tried 50 times by submit a new entry and got only 3 times passed. 47 another cases i got:
"Error sending Email via "192.168.2.20": 5.5.2 Need Rcpt command".
I run elogd -v and see:
"Email Team EUROPE to Shell execution not enable via -x flag"
    icon2.gif   Re: Conditional Email Notification by a text file, posted by Steve Jones on Fri Nov 3 03:42:18 2006 

An Thai wrote:

Steve Jones wrote:

An Thai wrote:
Hello,

I try to email by using a email text file to reduce the admin work.
  • MOptions Team = EUROPE, ASIA, AFRICA, AMERICA
  • Email Team EUROPE = $shell(type C:\EuropeEmailList.txt)

but i get always Email sent to Shell execution not enabled via -x flag

Is this feature not supported by ELOG or did i use the wrong syntax?

Thank you in advance.




Quote:
You need to start elogd with the "-x" flag


Yes, i did it. But the problem is still there.
I exactly tried 50 times by submit a new entry and got only 3 times passed. 47 another cases i got:
"Error sending Email via "192.168.2.20": 5.5.2 Need Rcpt command".
I run elogd -v and see:
"Email Team EUROPE to Shell execution not enable via -x flag"



Steve Jones wrote:

Well, it looks like you are getting the text "Shell execution not enable via -x flag" put into the EUROPE attribute then the email server is attempting to send email to the email address "Shell execution not enable via -x flag", which is clearly not a valid address thus the "Error sending Email via "192.168.2.20": 5.5.2 Need Rcpt command".

You need to run run "elogd -v -x" then look for the errors. You also might try a more simpler test like "Preset Team EUROPE = = $shell(type C:\EuropeEmailList.txt)" and then see what is returned. It makes it simpler and removes the email error from the equation.
    icon2.gif   Re: Bug? Password file location changed, posted by David Spindler on Fri Nov 3 14:40:36 2006 

Steve Jones wrote:

David Spindler wrote:

David Spindler wrote:
I just tried to upgrade from 2.6.1-1633 to 2.6.2-1734. Whenever I tried to access the elog, it showed my password to be invalid. I tried this on 2 machines and same results. I did notice on the second one when I started it from a command prompt that it was creating a new empty password file in a different location.

I have a password file called pwd.txt. It resides in the main elog directory, in my case, c:\elog, along with the elgod.exe and elogd.cfg. Apparently, the new version looks for it in the logbooks directory. I adjusted my path to the file and it works fine.

I am reporting this as a bug because it is my guess that this is not an expected result. I would expect the old elogd.cfg file to work without altering in the newer version.

Thanks, keep up the great work, Stefan. You have a great program.
David Spindler

I also just noticed that the text files I use for presetting the text window also have to be in the logbooks directory.



Quote:
The relocation was a documented change that Stefan made intentionally. Yes, it caught me too Smile

Thanks. I checked the changelog and the documentation for any such changes but did not see them. I just looked again, and still do not see them. Anyway, I know what to expect, now, and will adjust. Again, thanks!
icon5.gif   Push button for Menue Command, posted by An Thai on Fri Nov 3 15:53:44 2006 
Dear Stefan,

in your documentation: ELOG - Syntax of elog.cfg I see two screenshots in the Themes section. The left one shows a layout with Push buttons on the Menue Command. I would like this layout and try to find information on W3C consortium how i can redesign the CSS file to realise the push button for hyperlink, but I cannot get an success there. Can you give more information how you made it?

Thank you in advance
ELOG V3.1.5-3fb85fa6