| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1209
|
Wed Jun 22 18:34:18 2005 |
 | Gerfried Kumbartzki | kum@physics.rutgers.edu | Question | Linux | 2.6.0 | Re: Cloning | Thank you for the suggestions; I commented the read and write passwd in elogd.cfg out and only then I was able to clone
(elogd -v -C http://laptop:8080) the logbook to the new server.
But this is only part of the story. The logbook on the labtop is owned by the
default user elog and default group elog, that is needed to start up the elogd. Only a user "elog" can do the cloning, unless temporarily the owner ship in /usr/local/elog is changed. I made it work by temporarily changing the owner ship on both machines, did the cloning, changed back to owner elog, started elogd and all was running.
I setup synchronizing and here too it works only if the read passwd in elogd.cfg is commented out.
Sync works fine from the RedHat linux laptop (rpm installed), but crashes the elogd on the alpha Linux machine (compiled from src) most of the time. elogd hast to be restarted and the sync had not finished.
So for now I settled to do the synchronize only from the laptop but have to remove the read passwd each time. That is tolerable but not
convenient.
Here I have another question: My Elog is passwd protected, encrypted passwd in elogd.cfg (read and write). When connecting to the elog the window
pops up asking for a user name and the passwd. I donot remember exactly, what was done to set name and passwd. But I find it "strange" that the user name can be anything as long as the passwd is right to access the ELog.
I think I have to learn more about the whole user and passwd protection schema.
Thanks again
Gerfried |
|
1214
|
Fri Jun 24 21:24:55 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.6.0 | Re: Cloning |
| Gerfried Kumbartzki wrote: | But this is only part of the story. The logbook on the labtop is owned by the
default user elog and default group elog, that is needed to start up the elogd. Only a user "elog" can do the cloning, unless temporarily the owner ship in /usr/local/elog is changed. I made it work by temporarily changing the owner ship on both machines, did the cloning, changed back to owner elog, started elogd and all was running. |
The /usr/local/elog files should be owned by user elog on both machines, and both elogd daemons should be started under user elog. Since only the two elogd daemons communicate with each other during synchronization, that should be fine. Only after the initial cloning (which you presumably do under your own user account), you have to do a "chmod" to change ownership of all files to uid/gid "elog/elog".
| Gerfried Kumbartzki wrote: | | I setup synchronizing and here too it works only if the read passwd in elogd.cfg is commented out. |
As I said, the read password is not really supported for synchronization. It is there historically, from the times when there was no user level password access. If you use synchronization, you should use that authentication (by putting a "password file = ..." into your config.
| Gerfried Kumbartzki wrote: | | Here I have another question: My Elog is passwd protected, encrypted passwd in elogd.cfg (read and write). When connecting to the elog the window pops up asking for a user name and the passwd. I donot remember exactly, what was done to set name and passwd. But I find it "strange" that the user name can be anything as long as the passwd is right to access the ELog. I think I have to learn more about the whole user and passwd protection schema. |
If you switch to user level password access, this problem goes away as well.
- Stefan |
|
1358
|
Thu Jul 28 15:33:21 2005 |
 | Chris Howe | c.j.howe@rl.ac.uk | Bug report | Windows | 2.6.0 | Creating logbook by copying an existing one crashes elog | Hi,
Trying to create a new logbook from an existing one causes elog to crash.
output from DrMingw:
elogd.exe caused an Access Violation at location 00448c6e in module elogd.exe
Writing to location 6e206c65.
Registers:
eax=00240798 ebx=00000020 ecx=6e206c61 edx=00250088 esi=00000000 edi=69726500
eip=00448c6e esp=01c1a1d0 ebp=01c1a1f0 iopl=0 nv up ei ng nz ac po cy
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000297
Call stack:
00448C6E elogd.exe:00448C6E
00445F17 elogd.exe:00445F17
as the service restarts elog the browser then displays:
"Cannot open file elog.pwd: No such file or directory
Please use your browser's back button to go back"
If you try and create a new logbook from scratch (i.e. not a copy) then the browser displays:
"Cannot open file elog.pwd: No such file or directory
Please use your browser's back button to go back"
In both cases the new logbook is created.
any ideas?
Chris |
|
1362
|
Mon Aug 1 11:58:43 2005 |
| Kees Bol | kees.bol@wur.nl | Info | Linux | 2.6.0 | "full" only changes color | Hi,
I have the strange problem that when changing to "full"-diplaymode the output looks the same as with "summary", only the color is different. The texts don't appear.
Any idea what can cause this behaviour?
thanks
Kees Bol |
|
1364
|
Tue Aug 2 08:56:21 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | Linux | 2.6.0 | Re: "full" only changes color |
| Kees Bol wrote: | I have the strange problem that when changing to "full"-diplaymode the output looks the same as with "summary", only the color is different. The texts don't appear.
Any idea what can cause this behaviour? |
Can you send me your elogd.cfg ?
Have you made sure that the entries do contain some text? The behaviour you describe usually happens if you have entries without any text. |
|
1365
|
Tue Aug 2 10:25:32 2005 |
| Kees Bol | kees.bol@wur.nl | Info | Linux | 2.6.0 | Re: "full" only changes color |
| Stefan Ritt wrote: |
| Kees Bol wrote: | I have the strange problem that when changing to "full"-diplaymode the output looks the same as with "summary", only the color is different. The texts don't appear.
Any idea what can cause this behaviour? |
Can you send me your elogd.cfg ?
Have you made sure that the entries do contain some text? The behaviour you describe usually happens if you have entries without any text. |
Well, I guess that causes it. In the summary-view there is no visible text.
I thougt when choosing the full-view the text would appear along with the other attributes.
My config-file is:
================================================================
Theme = default
Attributes = Author, Type, Subject
Required Attributes = Type, Subject
Preset Author = $long_name
Locked Attributes = Author
Options Type = Question, Configuration, Problem, Info, Other
List Display = ID, Date, Author, Type, Subject
Thread display = $Subject, posted by $Author on $Date
Menu commands = Back, New, Edit, Delete, Reply, Find, Last 10, Change password, Logout, Help
Quick filter = Date, Type
Summary lines = 0
Start page = ?rsort=Date
; alleen eigen messages editen
Restrict edit = 1
====================================================================================== |
|
1372
|
Thu Aug 4 21:36:21 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.6.0 | Re: Creating logbook by copying an existing one crashes elog |
| Chris Howe wrote: | | Trying to create a new logbook from an existing one causes elog to crash. |
I (hopefully) fixed that bug. The fix will be included in 2.6.0-beta4. |
|
1374
|
Thu Aug 4 22:35:57 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | Linux | 2.6.0 | Re: "full" only changes color |
| Kees Bol wrote: | | I thougt when choosing the full-view the text would appear along with the other attributes. |
That's how it is supposed to be. I tried your config file, added three entries, and got the behaviour documented in the attached images. To me everything looks fine. |
| Attachment 1: summary.jpg
|
|
| Attachment 2: full.jpg
|
|
|