"Upgrading" from 1.35 to 2.52 fails, posted by PJ Meyer on Thu Apr 1 20:21:26 2004
|
Have a working copy of 1.35 running on NT4 server.
Went to upgrade to latest version.
Stopped service, installed the 2.52 version, restarted service and when
trying to connect get nothing but server not found, dns errors, etc.
Copy back the 1.35 elogd.exe and everything is fine - I can connect and add
entries to log.
Copy 2.52 elogd.exe and nothing.
So being the bright boy, I unistalled E-log, went through the registry and
yanked everything out that referenced ELOGD, rebooted, installed 2.52, made
the necessary registry changes, started service and nothing.
Stopped service and copied 1.35 Elogd.exe back into folder, started service,
and everything works.
Any ideas on why 1.35 works like a charm but 2.52 won't? I've tried stepping
back to 2.10 version before giving up.
This is a server that is patched to latest and runs quite well with 1.35. |
Re: "Upgrading" from 1.35 to 2.52 fails, posted by PJ Meyer on Fri Apr 2 02:41:36 2004
|
tuens out that the first log file was causing the problem. Elconv would just hang
on trying to convert it. renamed it, reran elconv, reload service and 2.51 elogd
and all was working as it should.
> Have a working copy of 1.35 running on NT4 server.
> Went to upgrade to latest version.
> Stopped service, installed the 2.52 version, restarted service and when
> trying to connect get nothing but server not found, dns errors, etc.
> Copy back the 1.35 elogd.exe and everything is fine - I can connect and add
> entries to log.
> Copy 2.52 elogd.exe and nothing.
>
> So being the bright boy, I unistalled E-log, went through the registry and
> yanked everything out that referenced ELOGD, rebooted, installed 2.52, made
> the necessary registry changes, started service and nothing.
>
> Stopped service and copied 1.35 Elogd.exe back into folder, started service,
> and everything works.
>
> Any ideas on why 1.35 works like a charm but 2.52 won't? I've tried stepping
> back to 2.10 version before giving up.
>
> This is a server that is patched to latest and runs quite well with 1.35. |
Global password file together with guest account, posted by Bertram Metz on Thu Apr 8 15:05:43 2004
|
Hello,
is it possible to have an guest account together with a global password file?
I tried to put the password file statement into the global section of
elogd.cfg. But in this case every user must login and it is not possible to
have a read only guest account.
But if I put the password file statemnet into the logbook sections, it is
possible to access the logbooks in read-only mode without logging in. The
drawback of this solution is, that you have to login into every logbook
seperately.
Bertram |
Re: Global password file together with guest account, posted by Stefan Ritt on Thu Apr 8 15:24:02 2004
|
> Hello,
>
> is it possible to have an guest account together with a global password file?
>
> I tried to put the password file statement into the global section of
> elogd.cfg. But in this case every user must login and it is not possible to
> have a read only guest account.
> But if I put the password file statemnet into the logbook sections, it is
> possible to access the logbooks in read-only mode without logging in. The
> drawback of this solution is, that you have to login into every logbook
> seperately.
>
> Bertram
Right, guest access is not possible with a global password file. This comes from
the fact that people wish to protect their logbook selection page. What I can do
is add another flag "protect selection page = 0 | 1". If "0", the logbook
selection page can be seen without logging in. Is that what yo want?
- Stefan |
Re: Global password file together with guest account, posted by Bertram Metz on Thu Apr 8 15:42:52 2004
|
> > Hello,
> >
> > is it possible to have an guest account together with a global password file?
> >
> > I tried to put the password file statement into the global section of
> > elogd.cfg. But in this case every user must login and it is not possible to
> > have a read only guest account.
> > But if I put the password file statemnet into the logbook sections, it is
> > possible to access the logbooks in read-only mode without logging in. The
> > drawback of this solution is, that you have to login into every logbook
> > seperately.
> >
> > Bertram
>
> Right, guest access is not possible with a global password file. This comes from
> the fact that people wish to protect their logbook selection page. What I can do
> is add another flag "protect selection page = 0 | 1". If "0", the logbook
> selection page can be seen without logging in. Is that what yo want?
>
> - Stefan
Yes, that is what I want.
Bertram |
Re: Global password file together with guest account, posted by Stefan Ritt on Thu Apr 8 16:23:00 2004
|
> Yes, that is what I want.
I implemented a switch "protect selection page" in revision 1.318, which can be
obtained at http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c?rev=1.318. If this
switch is not set to "1", the selection page can be seen without having to log in. |
Re: Global password file together with guest account, posted by Bertram Metz on Tue Apr 13 11:13:53 2004
|
> > Yes, that is what I want.
>
> I implemented a switch "protect selection page" in revision 1.318, which can be
> obtained at http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c?rev=1.318. If this
> switch is not set to "1", the selection page can be seen without having to log in.
Stefan,
thank you for the fast implementation of this feature. I compiled the new revision and
it worked as expected.
Kind regards,
Bertram |
CSV importing, posted by Paul Harrington on Fri Apr 23 11:50:07 2004
|
I have been importing data from a CSV file into elog which has worked.
However I'd like to import data from the CSV file, directly to the 'text'
field, rather than just to one an attribute fields. Is it possible to do
this?
Paul |
|