After entering a new user and activating it in ELOG, the new user receives an email.

The link does not work because the port number is repeated in the link (see below)

In the Global part of the elogd.ini we have added the port:

port = 8080



Maybe I am overlooking something, any suggestions are very much appreciated!



Thanks!

Ron



- - - - - -



Email Subject: Your ELOG account has been activated



Email Body:



Your ELOG account has been activated on host eloghost:8080.



You can access it at http://eloghost:8080:8080/logbookname/?unm=newuser.



To subscribe to any logbook, click on 'Config' in that logbook.

> After entering a new user and activating it in ELOG, the new user receives an email.
> The link does not work because the port number is repeated in the link (see below)
> In the Global part of the elogd.ini we have added the port:
> port = 8080
> 
> Maybe I am overlooking something, any suggestions are very much appreciated!
> 
> Thanks!
> Ron
> 
> - - - - - -
> 
> Email Subject: Your ELOG account has been activated
> 
> Email Body:
> 
> Your ELOG account has been activated on host eloghost:8080.
> 
> You can access it at http://eloghost:8080:8080/logbookname/?unm=newuser.
> 
> To subscribe to any logbook, click on 'Config' in that logbook.

I just tried myself and got:



Your ELOG account has been activated on host localhost:8080.

You can access it at http://localhost:8080/Demo/?unm=midas.

To subscribe to any logbook, click on 'Config' in that logbook.



I used following config:

[global]
Port = 8080
Password file = passwd
SMTP host = xxx
Self register = 3
Admin user = stefan
 
[Demo]
Attributes = Type, Subject, Author


So something in your config file must be different. Can you find out what it is?

/Stefan

Hi Stefan, thank you very much for having a look at this :-)



Here is the config file we use. Seems okay to me, but I may be overlooking something.





[global]

port = 8080

SMTP host = localhost

Self register= 0

Display Email recipients = 0

Use Email Subject = [ELOG - $logbook]

Date format = %a %d-%b-%Y %H:%M

Default encoding = 1

Allowed encoding = 1



[MYLOGBOOK]

Theme = default

Comment = My logbook

Password file = passw_mylogbook.pwd

Admin user = admin,user1,user2,user3

Self register= 3

Menu commands = List, New, Edit, Reply, Duplicate, Find, Config, Logout, Help

Attributes = Author, Type, Category, Subject, ServerNaam

Preset Author = $long_name

Options Type = Opt01, Opt02, Opt03, Opt04, Opt05

Options Category = Cat01, Cat02, Cat03, Cat04, Cat05, Cat06, Cat07

MOptions ServerNaam = Server01

Preset ServerNaam = Server01

Required Attributes = Author, Type, ServerNaam

Page Title = ELOG - $subject

Reverse sort = 1

Quick filter = Date, Type, ServerNaam

 Hi i am new here,

No, only "Fixed Attributes Reply".  

 OK :-|

Thanks for the quick response

 I'm having an issue with ELog 2.9.2 revision 2455 where it crashes consistently with:

*** glibc detected *** /usr/local/sbin/elogd: malloc(): memory corruption: 0x0000000014977210 ***

 Is it possible to change the "yellow" background color when running a search ? (I looked in the css, there is nothing...) 

Couldn't find any syntax for elogd.cfg

Thanks for your help :)

There are no specific classes for the search dialog, but you can play with the classes "form2", "attribname" and "attribvalue". These classes are used in several places, so all will change in the same way, but maybe that's what you like. 

 Understand.. So when a search/sort is done, the searched item come up with a yellow background... 

The thing is, if you set a "Cell Style XXX= background-color: ZZZ" it become useless since it is replace with the yellow background.

I tried to play with the css but I couldnt figure it out... So you say I cant do anything about it ? I'm just wondering where this yellow color comes from :)

vs the way I would like it to be :

 Good day,

I have 2 logbooks. The main one and the one for the archived entries.

I can make a "move to" command in the main one witch will bring the drop down for the archive. (working perfect).

I was wondering if it is possible to make a "custom" move to in witch I can directly specify the destination logbook, hide the drop down and rename the button.

The main objective is to make a button called "Archive" witch the users only have to press to move the selected entries.<

I know I can make some custom command in list view ie :<a href="?xxx=xxx1|xxx2">zzz</a> so I was wondering if the same is possible and if so, can you guide me on the syntax ?

Thanks for your help :)

 Good day,

I was wondering (and I searched for :) ) a way to directly edit an entry while in summary view instead of having to first click on the entry then click on Edit...

I mean, in summary view, every row entry is clickable to access the entry itself (except email witch open email client), so instead to open it, can it be edited directly ?

Is it possible ?

No, this is not possible. 

Is there a way of having multiple copies of elog running on one windows 2003 server? different ports?

I need to access 2 different elogd.cfg files.

 It's probably not of much help, but for a short time I ran two elog daemons on the same linux box, using different ports.  It was thus able to run with two separate elogd.cfg files.   This is linux, and heavily biased to my eccentric way of running this linux box, but started them as:

/usr/local/sbin/elogd -p 8080 -c /home/logbooks1/elogd1.cfg -d /home/logbooks1

/usr/local/sbin/elogd -p 8081 -c /home/logbooks2/elogd2.cfg -d /home/logbooks2

Do note that as I was the only user on that linux box, I didn't have login etc.

However, I was soon asked questions by Andreas as to how I found this running, as he had encountered problems with an earlier version.  To be honest, that stopped me experimenting too far with this at that point, as well as a coincidental upgrading of my hardware.

But I was doing this *not* because I had to run two separate elogd.cfg files, but other reasons which meant splitting into two at that time vastly improved the performance of elog on the linux box at that time.  So while I didn't actually enounter any problems in doing so, I only have limited experience - and, of course, absolutely none on running even one [windows equivalent of a daemon] on Windows.

I am assuming here you have good reason for two separate elogd.cfg files, rather than just wanting to run two separate logbooks - guessing here, but one set public (no login) and one set private (with login)?

 

 I need to do this because there are 2 different groups that each have 6 or 7 different logbooks in their elogd.cfg files.  (and they can't access each others log books)

Currently the first group  accesses elog as http:elog.com:8080.  The elogd windows service executes "C:\Program FilesELOG\elogd.exe" -D -c "C:\Program Files\ELOG\elogd.cfg"  

From what I can tell, whats needed is either some way to get the windows service to run a different config file or there needs to be a way of creating a second elog windows service that points to a different elogd.cfg file. Is there some way of doing this?

Have you checked the option "Top groups", which was made especially for that case? You can create several independent sets of logbooks not seeing each other. 

 I will check out the "Top Groups". But another question, the documentation says "Prior to ELOG version 2.4.1, one had to run two elogd servers in parallel, listening under different ports." ... how do you set this up?

You have to create manually a second service. Clone all entry from the first one, except the command line where you load a different elogd.cfg. But I actually never tried this myself. 

Just for completeness: I was running two elogd servers (2.9.0) on one Linux host in order to provide an english and a german web interface to the same logbooks, synchronised by the mirror server mechanism.

That didn't work out well, the elogd crashed infrequently. But of course mirror servers are not intended to run on the same host. Eventually I've just dropped the english server.

Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish

Detect language » English

 

 Is there any way within eLog to undelete entries?

No. 

 I wrote to scripts to backup the logbook files:

• elog_backup_daily creates a tar file of all new entries of the last 25 hours and keeps these backups for 90 days
• elog_backup_hourly creates a tar file of the entries of the last 65 minutes and keeks these backups for one week
• exclude-logbooks specifies which files not to backup

This allows you at least to recover deleted entries by hand as an administrator.

Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish

Detect language » English

 

Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish

Detect language » English

 

Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish

Detect language » English

 

Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish

Detect language » English

 

Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish

Detect language » English