Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 363 of 806  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Icon Author Author Email Category OS ELOG Version Subject
  66906   Wed Sep 15 01:54:56 2010 Reply David PilgramDavid.Pilgram@epost.org.ukQuestionLinux | All2.8.0-2313Re: Searching Logbooks
Hi Stefan,

I was rather hoping that was *not* going to be your answer.

I much prefer the plain ascii file format, for it allows me to edit it for "mistakes" post submission, 
shall we say. 

> > Hi Stefan,
> > 
> > I'm starting to get a similar problem to Lance's ("SQL Database").  Searching is beginning to take time.
> > 
> > In searching, I either can search one logbook (still relatively quick), or all of them.
> > 
> > I have my logbooks in groups, and often I know which group I want to search, and it would make the searching
> > much quicker were the search confined to just that group.  I don't think I've missed anything in the
> > documentation on this matter.  
> > 
> > If not a change to the elog program, is there another way of (say) arranging the logbooks that will achieve this?
> 
> You can't do that right now. I would have to extend the functionality to allow searching in groups. Also have a look 
> at https://midas.psi.ch/elogs/Forum/66901. Maybe that helps a bit in meantime.
  66905   Wed Sep 15 01:25:27 2010 Reply Stefan Rittstefan.ritt@psi.chQuestionWindowsELOG V2.8Re: how to change char encode for Text column

phichitpon wrote:

hello

how to change char encode for Text column. my language is thai and use tis-620 for encode. thankyou

Just use the charset = xxx option in the configuration file. 

  66904   Wed Sep 15 01:04:21 2010 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.7.8Re: honor "user" field in the Apache SSL request object or environment variables in SSL process groups?

Owen LaGarde wrote:

Will elog defer user identification and authorization to the ssl engine of a *local* Apache proxy?  I'd like to try elog in a site that requires the service port positively authenticate and identify users via smartcard certificate ID.  Per SOP they have Apache+mod_ssl setting SSLUserName=SSL_CLIENT_S_DN_CN which sets both the SSL request object's "user" field and the REMOTE_USER environment var relative to the mod_ssl's session's process group leader.  Users auth with Apache's mod_ssl as a single-signon replacement for web apps which have traditional native, internal user accounts/passwords, but those passwords are subsumed by the Apache/smartcard/mod_ssl setup.  The web apps define internal accounts matching the users' cert IDs but do not allow any management of the [unused] passwords.  Can elog do this?

This is not implemented at the moment. 

  66903   Wed Sep 15 01:02:26 2010 Reply Stefan Rittstefan.ritt@psi.chQuestionWindowsV2.8.0-231Re: how to convert Common Era (C.E.) into Buddhist Era

phichitpon wrote:

how to convert Common Era (C.E.) into Buddhist Era  such as C.E. 2010 to B.E. 2553   (2553=2010+543) .thank you

Uh, thank you for teaching me that something like B.E. exists. I didn't know before. Unfortunately elog relied on the underlying operating system date functions. I guess you have to convince Windows or Linux to switch to B.E., then elog will do as well. 

  66902   Wed Sep 15 00:32:48 2010 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux | All2.8.0-2313Re: Searching Logbooks
> Hi Stefan,
> 
> I'm starting to get a similar problem to Lance's ("SQL Database").  Searching is beginning to take time.
> 
> In searching, I either can search one logbook (still relatively quick), or all of them.
> 
> I have my logbooks in groups, and often I know which group I want to search, and it would make the searching
> much quicker were the search confined to just that group.  I don't think I've missed anything in the
> documentation on this matter.  
> 
> If not a change to the elog program, is there another way of (say) arranging the logbooks that will achieve this?

You can't do that right now. I would have to extend the functionality to allow searching in groups. Also have a look 
at https://midas.psi.ch/elogs/Forum/66901. Maybe that helps a bit in meantime.
  66901   Wed Sep 15 00:21:10 2010 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.7.6-2230Re: SQL Database

lance wrote:

We have been running elog for a few years now and its solid. The only thing is we are getting to 140k entries over a few books and its starting to slow down whist searching. My questions is can we go to an SQL type database rather than a flat file? Is it worth it? Is anyone running this type of configuration?

Running through a SQL database requires a major rework of the software. I'm planning this in the long run, but not for this year. I'm also not sure how much this would buy you. If you do a full-text search on 140k entries in a SQL database (not index search), this might also take some time.

But what you can do is to "archive" part of your logbooks. Since the files are named YYMMDDa.log, you can move all 09XXXXXa.log files into a separate "archive" which you then do not include in your search.  

  66900   Tue Sep 14 23:29:15 2010 Reply Stefan Rittstefan.ritt@psi.chQuestionLinuxELOG V2.8.Re: Password problem after elogd restart

Jack Dapid wrote:

Hi.

I have ELOG V2.8.0-2313 installed on a SLC 5.5 release and all works fine, Users can register them-self and I see for each of them in the passwd file:

<name>test</name>

<password>***something***</password>

....

 

after a '/etc/rc.d/init.d/elogd restart' the logins don't work anymore (they did before the restart)

and the passwd file changed:

<name>test</name>

<password encoding="SHA256">***something else***</password>

....

 

Any idea what goes wrong?

Cheers, Jack

Please have a look at https://midas.psi.ch/elogs/Forum/66872 

  66899   Tue Sep 14 11:58:22 2010 Warning Jack Dapiddaniel.dobos@cern.chQuestionLinuxELOG V2.8.Password problem after elogd restart

Hi.

I have ELOG V2.8.0-2313 installed on a SLC 5.5 release and all works fine, Users can register them-self and I see for each of them in the passwd file:

<name>test</name>

<password>***something***</password>

....

 

after a '/etc/rc.d/init.d/elogd restart' the logins don't work anymore (they did before the restart)

and the passwd file changed:

<name>test</name>

<password encoding="SHA256">***something else***</password>

....

 

Any idea what goes wrong?

Cheers, Jack

ELOG V3.1.5-3fb85fa6