| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
2036
|
Thu Nov 2 23:17:10 2006 |
 | Steve Jones | steve.jones@freescale.com | Bug report | Windows | 2.6.2-1734 | Re: Bug? Password file location changed |
| 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  |
|
|
2038
|
Fri Nov 3 03:42:18 2006 |
| Steve Jones | steve.jones@freescale.com | Question | Windows | 2.6.2.1723 | Re: Conditional Email Notification by a text file |
| 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.
|
|
|
2045
|
Mon Nov 6 19:03:11 2006 |
 | Steve Jones | steve.jones@freescale.com | Request | Other | 2.6.2-1739 | Option to require new user registration to subscribe to ALL logbooks |
Stefan, any chance of having an option that eliminates the ability of new users to pick the logbooks they can register with? I would like to limit this to the "admin" user to pick per individual.
Also, any thoughts to adding a management panel that will the admin user to make global changes to the password file? I do this by bringing it into a text editor and making changes, but it would be nice to do it from the application. |
|
2051
|
Wed Nov 8 12:55:58 2006 |
| Steve Jones | steve.jones@freescale.com | Bug report | Other | 2.6.2-1714 | SVN1723-overiding logbook directory causes eLog to bomb when going into daemon mode (was SVN1714 will not run in 'daemon" mode on Solaris8) |
| Stefan Ritt wrote: |
| Steve Jones wrote: | BUG: In the initial comment section of elogd_fancy.cfg the line # This [global] section contains settings common to all logbooks is not parsed correctly as a comment and the embedded [global] is picked up and confuses elogd, eg., elogd will not pickup the port=8080 option. Taking "[global]" out of the comment restores fucntionality. I recommend checking to make sure that the config file checking routine ignores *entire* lines starting with a comment char; |
Acknowledged. The problem was that the section between the line # This [global] section contains settings common to all logbooks and the real [global] section was interpreted as the global section, and thus the "real" one was omitted. I changed the code now such that all lines starting with a '#' or ';' are completely skipped, that fixes the problem. The fix is contained in revision 1745.
| Steve Jones wrote: | ISSUE: The option Logbook dir = causes an enormous amount of problems, and this may be limited to elog installs that exist in NFS space (as opposed to local disk). If the default is left alone elogd appears to work fine; Try and override and the fun begins. The previous attached traces show that once going into daemon mode none of the logbook dirs can be found nor indexed. The workaround is to use the default "logbooks" dir. Perhaps the routine that creates the default (if not found) should be the same as the one that creates the override (?). |
That's weird. Have you tried to specify a full path for the logbook, like /nfs/some/directory ? The only difference of the daemon mode compared to the normal mode is that elogd does a cd to the root ('/'). If you specify logbook dir relative to the starting directory, like 'some/subdir', elogd will the try to access it under '/some/subdir', where it might not have read/write privileges. |
| Quote: | Very weird. No, I did not try an absolute path - but I did notice the attempt to "cd /" in the truss output. In fact, it was immediately after that "cd /" test that things appeared to start not working - basically, elogd could not find anything.
I'm putting this on hold for the time being as I now have test systems going into production. I'll be able to test next week.
|
|
|
2066
|
Thu Nov 9 23:37:37 2006 |
| Steve Jones | steve.jones@freescale.com | Request | Other | 2.6.2-1739 | Re: Option to require new user registration to subscribe to ALL logbooks |
| Stefan Ritt wrote: |
| Steve Jones wrote: | | Stefan, any chance of having an option that eliminates the ability of new users to pick the logbooks they can register with? I would like to limit this to the "admin" user to pick per individual. |
The logbook list new users can register with is exactly the list the users have access to. So if you omit a logbook there, they can later just go to that logbook, hit config, and add themselves. If you want to prevent a user from getting notifications from a logbook, prevent user access to that logbook, like a new top group.
| Steve Jones wrote: | | Also, any thoughts to adding a management panel that will the admin user to make global changes to the password file? I do this by bringing it into a text editor and making changes, but it would be nice to do it from the application. |
Not at the moment. It would take days of work which I don't have right now. Much more than what it takes you editing the password file in an editor  |
| Quote: |
Hmm, by default all users have access to all logs. What I have setup is an announcement logbook and I would simply like to send to all registered users the email when announcements happen. My thought was to simply not allow people to pick which logbooks to "register" with and default to the Announcements logbook. I went ahead and hacked the password file and simply set all accounts to subscribe to all logbooks 
|
|
|
2070
|
Fri Nov 10 12:55:38 2006 |
| Steve Jones | steve.jones@freescale.com | Info | Windows | V2.6.2-175 | Re: Outlook, Outlook Express and Free Webmail have problem with <br /> |
| Stefan Ritt wrote: |
| An Thai wrote: | If users reply an entry, the notification email cannot be displayed correctly in Outlook, Outlook Express and Webmail.
I look at the source code and see <br />. It could be the reason. |
<br /> is XHTML standard and valid code. I do not have this problem in Mozilla Thunderbird. |
| Quote: |
I've noticed teh same in Outlook and attribute it to MS' attempt to deal with HTML -- this was not an issue until a recent Outlook upgrade at our company.
The problem is with Outlook and MS' email clients.
|
|
|
2178
|
Wed Mar 28 21:00:17 2007 |
 | Steve Jones | steve.jones@freescale.com | Bug report | All | Other | 2.6.2-1739 | "Guest menu commands" not changing the menu line |
I tried adding the lines below to my Global section, and while Guest access is turned on the menu line does not change. I tried searching SVN change logs for a comment regarding any 'guest' bugs but found nothing. Was this a problem at some point and fixed? I noticed that the Midas site is running 2.6.4-1814 and the guest menus work! Am I doing something wrong or was this a problem in the past?
Thanks!
Guest menu commands = List, Find, Login, Help
Guest List Menu commands = List, Find, Login, Help |
|
2179
|
Thu Mar 29 23:03:26 2007 |
| Steve Jones | steve.jones@freescale.com | Bug report | All | Other | 2.6.2-1739 | Re: "Guest menu commands" not changing the menu line |
| Steve Jones wrote: | I tried adding the lines below to my Global section, and while Guest access is turned on the menu line does not change. I tried searching SVN change logs for a comment regarding any 'guest' bugs but found nothing. Was this a problem at some point and fixed? I noticed that the Midas site is running 2.6.4-1814 and the guest menus work! Am I doing something wrong or was this a problem in the past?
Thanks!
Guest menu commands = List, Find, Login, Help
Guest List Menu commands = List, Find, Login, Help |
| Quote: |
Ok, well, I built version 2.6.4-1795 and I have the same issue -- Guest menus do not show up when added to my configuration.
Suggestions on where to look? Start from scratch?
|
|