Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 292 of 808  Not logged in ELOG logo
 Find |  Login |  Help 
New entries since:Thu Jan 1 01:00:00 1970
 Full | Summary | Threaded | Hide attachments  Show all entries    6457 Entries 
Goto page Previous  1, 2, 3 ... 291, 292, 293 ... 806, 807, 808   Next  
ID Date Icon Authordown Author Email Category OS ELOG Version Subject
  66560   Fri Oct 16 12:17:15 2009 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.7.7Re: User authorization file corruption

soren poulsen wrote:

Hi,

Here is what happens (I think) if E-log encounters a full file system where it keeps the user authorization file:

1. When a user connects, E-log will make a backup of the file. The backup will be corrupt since the file system is full.

2. E-log will modify the contents of the original file, and write it back. The file will be corrupt since the file system is full.

3. Now, both the backup and the normal file are corrupt and you cannot log on, until someone cleans up the file system and restores a valid copy of the file.

Would it be possible to fix this ? Like abort if step 1 is not successful. And restore the backup file if step 2 is not successful.

Thanks a lot for you help 

Soren

Ok, I finally found some time (I'm pretty busy these days) to add a check for a potential full file system in SVN revision 2258. So before the password file would get corrupted, elog shows an error message about the full file system and just stops to work until space is freed up. 

  66561   Fri Oct 16 12:21:45 2009 Reply Stefan Rittstefan.ritt@psi.chRequestLinux2.7.7Re: Option list length

soren poulsen wrote:

Hi,

I use the following attribute definition:

Options <attribute> = <list> 

However, I am being limited by the list length limit of 100. I have 103 items, but I only see 100.

Could the limit be extended (to 200 for instance) ?

Thanks a lot for your help

Soren

You can change that yourself. Just find following line in elogd.c:

 

#define MAX_N_LIST      100

and change it to 200, then recompile. But you are there on your own, at some point you will get a stack overflow and elogd will crash, but I don't know exactly where this limit is.
 
Anyhow I would propose that if you have so many options in an attribute, that you better go and group these options somehow. Like using two attributes, where the first defines the group, and the second gets different list for each option of the first attribute using conditional attributes. Have a look here.

 

 

  66562   Wed Oct 21 19:06:59 2009 Reply Stefan Rittstefan.ritt@psi.chRequestAll2.7.7Re: feature req.: identify ELOG web pages via META element

Bill Pier wrote:

 

* Withdrawn *

The HTML layout produced by elogd is horrendous to deal with programmatically; I give up.

 

 

Hi,

I'm writing a greasemonkey script to slightly alter the look of the pages served by the ELOG server.  One difficulty that I'm struggling with is how to identify what type of page ELOG has created.  While I have several methods to determine the page type, such as a log entry vs. log entries summary, the solutions are not straight forward and not clean.  As far as I tell, there's no specific identification in HTML document currently that describes and identifies the type of page being served by the ELOG server.

So, I'm requesting that the pages created by ELOG be identified in some fashion with the META element, such as:

    <meta name="description" content="elog log entry" />

or

    <meta name="description" content="elog log summary" />

 

or even using the keywords attribute:

    <meta name="keywords" content="elog log summary" />

Sorry, I didn't yet have time to implement your request.

Have you considered to download an entry in plain text? Like this entry you can load with

https://midas.psi.ch/elogs/Forum/66555?cmd=Download

which should be much easier to interprete. If you write your entries in ELCode or plain format, it should be even easier. 

  66572   Tue Nov 3 09:04:34 2009 Reply Stefan Rittstefan.ritt@psi.chBug reportWindows2.7.7 2246Re: 2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5

David Spindler wrote:

I upgraded 2.7.5 rev 2175 to 2.7.7 rev 2246 last Thursday. I tested it with several logbooks with no problems. However I received a rep[ort today that it was down. I discovered whenever I tried to open a logbook entitled "Equipment Reservation" in the folder "EquipmentReservations" Elog would crash. I checked the elog.log file with no entries in it other than showing when it was restarted. I backed up to 2.7.5 and had no porblems with the same logbook. I repeated the upgrade to 2.7.7 with the crash problem returning. I am now back on 2.7.5 with no problems.

 

I just decided to try 2.7.6 rev 2239 and had the same results as 2.7.7.

 

This is running under Win2K with SP4 as an automatic service on port 80.

 

I am also running Elog V2.7.4-2118 on a different port (8080) simultaneously with no problems.

 

If you wish I will send the elog.cfg file. Anything else I can do to help, please let me know.

I need to reproduce your problem. Therefore I need the configuration and the xxxxxxa.log file containing the offending entries. You can strip it down to the minimum needed to do the crash. 

  66573   Tue Nov 3 09:14:14 2009 Reply Stefan Rittstefan.ritt@psi.chCommentLinux2.7.7-2254Re: Emails generated by *this* discussion forum
> Hi Stefan,
> 
> After 21.Oct, all the emails sent out by this discussion form now are addressed to
> 
> ELOG@ananke.jtan.com
> the name of the server my mails are sent to.
> 
> Before that the emails were addressed to 
> 
> ELOG@emix.psi.ch
> 
> Obviouisly my real email address is there, in the headers (as it would appear for a BCC)
> 
> The only consequence for me was these emails turned up in the wrong mailbox, but perhaps it has wider implications?

Indeed on Oct. 21st the SMPT server sending out emails from this forum has been changed. I checked my own mails coming 
from the forum, but I could not find any hint of what you describe above. The "From:" header contains "noreply@psi.ch" 
and the "To:" header is my email address. The "Received:" header contains our SMTP server, but you should not that field 
for filtering your email.

- Stefan
  66574   Tue Nov 3 09:24:15 2009 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.77Re: Access control, group level

Niklas wrote:

Hi elog experts =)

 

Anyone know if it's possible to have access control per group-level?

For instance:

Group A = B,C   

Group B = LogA   

Group C = LogB, LogC      

Group C: Read password = abc

 //NH

I added your vote to the wishlist

https://midas.psi.ch/elog/wishlist.html 

  66580   Fri Nov 6 13:46:38 2009 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.7.7.1Re: width of the Text column in the summary list view

Fabio Rossi wrote:

I have "Summary lines = 1" in the config file. The first line visualized in the summary list, in the Text column, is truncated. I'm using the default style.

Which is the way to set the number of character displayed?

I added a new parameter

Summary line length = x

for you. This is included in SVN revision 2262 (if you can compile it yourself) and will be contained in the next release.

  66587   Tue Nov 10 12:54:47 2009 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.7.5-2130Re: Export Text to a csv File

Michael Dannmeyer wrote:

Hello,

is it possible to export the Text Field and the entries in this field to a csv file? If yes, what are the settings to do this?

Regards

Michael

A CSV file is by definition one line per entry. So if you have several lines in your Text Field, how will you be able to squeeze this into one line?

Alternatively you can export to XML, which contains the Text Field, then do a manual conversion to something else. 

Goto page Previous  1, 2, 3 ... 291, 292, 293 ... 806, 807, 808   Next  
ELOG V3.1.5-3fb85fa6