how to set text column width, posted by phichitpon on Fri Oct 8 04:53:50 2010
|
hello
how to set text column width in Elog
thank you |
Re: how to set text column width, posted by Stefan Ritt on Fri Oct 8 09:19:13 2010
|
phichitpon wrote: |
hello
how to set text column width in Elog
thank you
|
There is currently no easy possibility to change this except manually changing the CSS file. But that requires some CSS and HTML knowledge. You would have to change the CSS class "listtitle2" and "summary". |
SQL Database, posted by lance on Thu Sep 2 10:30:14 2010
|
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? |
Re: SQL Database, posted by Stefan Ritt on Wed Sep 15 00:21:10 2010
|
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. |
Re: SQL Database, posted by Bill Pier on Thu Sep 23 17:22:43 2010
|
What about using something like MySQLfs to get a db backend transparently to ELOG? I use ENCFS, (a FUSE backend), currently to achieve encrypted logbooks and it works fine -- ELOG never knows anything other than reading and writing to logbook files. From what I've read, the MySQLfs backend would work the same, and you likely would gain some of the caching benefits of MySQL, which might help with your read/search times, given the memory requirements of the database of course.
Bill
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?
|
|
Cannot bind to port 8080, posted by marco meneghelli on Fri Sep 17 14:54:51 2010
|
good morning,
I have installed elog 2.8.0 from terminal but when I type
elogd -p 80
or simply
elogd
the system tells me
Cannot bind to port 8080
Can someone help me?
Thanks
Marco M |
Re: Cannot bind to port 8080, posted by Stefan Ritt on Mon Sep 20 14:54:21 2010
|
marco meneghelli wrote: |
good morning,
I have installed elog 2.8.0 from terminal but when I type
elogd -p 80
or simply
elogd
the system tells me
Cannot bind to port 8080
Can someone help me?
Thanks
Marco M
|
Under linux, only the "root" user can start programs on ports below 1024. If you get problems binding to ports above 1024 (such as 8080) it means that some other program uses already that port. You can check what is running usually with
netstat -l -p
|
Searching Logbooks, posted by David Pilgram on Thu Sep 2 12:40:03 2010
|
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? |
Re: Searching Logbooks, posted by Stefan Ritt on Wed Sep 15 00:32:48 2010
|
> 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. |
Re: Searching Logbooks, posted by David Pilgram on Wed Sep 15 01:54:56 2010
|
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. |
how to change char encode for Text column, posted by phichitpon on Thu Aug 19 08:36:11 2010
|
hello
how to change char encode for Text column. my language is thai and use tis-620 for encode. thankyou |
Re: how to change char encode for Text column, posted by Stefan Ritt on Wed Sep 15 01:25:27 2010
|
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. |
honor "user" field in the Apache SSL request object or environment variables in SSL process groups?, posted by Owen LaGarde on Wed Aug 25 02:49:44 2010
|
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? |
Re: honor "user" field in the Apache SSL request object or environment variables in SSL process groups?, posted by Stefan Ritt on Wed Sep 15 01:04:21 2010
|
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. |
how to convert Common Era (C.E.) into Buddhist Era , posted by phichitpon on Wed Aug 25 09:18:39 2010
|
how to convert Common Era (C.E.) into Buddhist Era such as C.E. 2010 to B.E. 2553 (2553=2010+543) .thank you |
Re: how to convert Common Era (C.E.) into Buddhist Era , posted by Stefan Ritt on Wed Sep 15 01:02:26 2010
|
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. |
Password problem after elogd restart, posted by Jack Dapid on Tue Sep 14 11:58:22 2010
|
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 |
Re: Password problem after elogd restart, posted by Stefan Ritt on Tue Sep 14 23:29:15 2010
|
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 |