In a test area we loaded elogd 2.9.0 built Mar 21 2011, 08:48:02 revision 2396

During our testing we started the creation of a new elog, then backed out cancelling the creation and received the following error.

Error: Too many parameters (> 120). Cannot perform operation.

We do not see this error in the older version.

Hi,

We've recently implemented the Copy To function and it works as advertised. The issue we're having is the original entry time is also copied, so if we take an old log and copy it to another log book the entry using reverse sort, preserve = 0 may not display as the newest id. It will receive the next message id, but not display in the correct order on the page. Is there an option or parameter that will force Copy To create a new entry time, so the message id will appear in the correct order?

Thanks,
Mike

Hi,

We've recently implemented the Copy To function and it works as advertised. The issue we're having is the original entry time is also copied, so if we take an old log and copy it to another log book the entry using reverse sort, preserve = 0 may not display as the newest id. It will receive the next message id, but not display in the correct order on the page. Is there an option or parameter that will force Copy To create a new entry time, so the message id will appear in the correct order?

Thanks,
Mike

Hi,

We've recently implemented the Copy To function and it works as advertised. The issue we're having is the original entry time is also copied, so if we take an old log and copy it to another log book the entry using reverse sort, preserve = 0 may not display as the newest id. It will receive the next message id, but not display in the correct order on the page. Is there an option or parameter that will force Copy To create a new entry time, so the message id will appear in the correct order?

Thanks,
Mike

I currently have an Attribute defined in my .cfg file as  "Format <Attribute> = 0, attribname, attribvalue, 120, 500". I've found if I exceed 255 characters elogd.exe fails. Is there a method that will allow me to exceed 255 characters?

I currently have an Attribute defined in my .cfg file as  "Format <Attribute> = 0, attribname, attribvalue, 120, 500". I've found if I exceed 255 characters elogd.exe fails. Is there a method that will allow me to exceed 255 characters?

Hello,

I'm new to elog. I've installed it under Slackware 11. Everything worked smoothly until I wanted to establish access control. I followed the steps described under Access control heading in Syntax of elog.cfg chapter. I specified a new password file name and the following steps with no problem. After having created a new user I stopped elogd  and added  Admin user to config file. And here is my problem - each time I want to login to elog, I get "Invalid user name or password!" message. The meaning of it is obvious. So I have repeated all the steps several times. Of course I paid attention to enter user name and password correctly but I can't get rid of this message. For sure I making something wrong, but what it is ?

Here is part of my elogd.cfg:

[global]
Port=8080
Logfile = elogd.log
Logging level = 3
Password file = passwd
Self register = 1
Admin user = eloga
charset = utf-8
 

Here is what happens after elog restart:

elogd 2.8.0 built Oct 22 2010, 11:04:31 revision 2313
Falling back to default group "elog"
Falling back to default user "elog"
Falling back to default group "elog"
Falling back to default user "elog"
ImageMagick detected
Indexing logbooks ... Converting password file for logbook "Demo" to new encoding ... ok
done
Server listening on port 8080 ...

Here is the password file :

<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- created by MXML on Wed Nov 24 13:13:43 2010 -->
<list>
  <user>
    <name>eloga</name>
    <password encoding="SHA256">vnpfrWa8wmxFsLFjlY/poXdz3wh6RLt9BT.D1O52Xl9</password>
    <full_name>Mariusz Stakowski</full_name>
    <last_logout>0</last_logout>
    <last_activity>Wed Nov 24 13:13:43 2010</last_activity>
    <email>Mariusz.Stakowski@asseco.pl</email>
    <email_notify/>
  </user>
</list>

And here is what I found in elogd.log file:

24-Nov-2010 13:50:06 [] Server listening on port 8080 ...
24-Nov-2010 13:50:53 [eloga@xx.xx.xx.xx] {Demo} LOGIN user "eloga" (attempt)

Could somebody help me please ?

Best regards

Mariusz Stakowski

 Thank you Stefan, it works now

Best regards

Mariusz Stakowski