Re: Fail to install in mac, posted by Stefan Ritt on Fri Feb 13 19:47:43 2015 
|
Sorry I forgot to include the elogd.plist file in the distribution. I attached it to this entry, so just copy it into the elog root directory and run again "make install".
/Stefan
| Alex wrote: |
|
Hi
I am trying to install to mac 10.10.2 - everything works almost fine, but when I issue the sudo make install I get
Installing example logbook to /usr/local/elog/logbooks/demo
install: logbooks/demo/2001/011108a.log -> /usr/local/elog/logbooks/demo/2001/011108a.log
install: elogd.plist: No such file or directory
make: *** [install] Error 71
Any idea why ?
Thanks
Alex
|
|
|
Re: Fail to install in mac, posted by Stefan Ritt on Fri Feb 13 21:18:46 2015
|
Point your browser to http://localhost:8080 as written in the documentation
| Alex wrote: |
|
Thanks! now install works fine - but I cannot find how to open and start writing- I do
/usr/local/sbin/elogd
elogd 3.0.0 built Feb 13 2015, 16:42:32 revision 21dc563
CKeditor detected
ImageMagick detected
Indexing logbooks ... done
Server listening on port 8080 ...
but nothing pops up...I mean it is not possible to run "offline" ie locally on my mac ?
|
|
|
Re: Enter past date for logbook, posted by Stefan Ritt on Wed Feb 25 07:52:21 2015
|
No. The date/time tag is there to actually document the time when the log was made. If you are late, you are late.
| Banata Wachid Ridwan wrote: |
|
Is it possible to enter past date in logbook
I forgot to enter log yesterday, is it possible to add up now?
|
|
|
Re: Elog stability with multiple users, posted by Stefan Ritt on Thu Feb 26 10:39:58 2015
|
By desing, there is no collision between different users, since all requests are executed in sequence (single thread). The only problem is that the server becomes unavailable for others if it executes a long search. This is why most users of large lobooks restrict their search to let's say the last month or so by default. This speeds up the search and limits the dead time for others. This can be done via the show last default = <days> directive.
| Alan Grant wrote: |
|
Are there any known or reported daemon stability issues with an increase of concurrent users logged in to view and search entries, while the elog client is also adding 5 to 10 new entries every minute during a peak 2-hour period each day?
|
|
|
Re: Elog stability with multiple users, posted by Stefan Ritt on Mon Mar 2 08:06:38 2015
|
Being not able to kill a server running in an endless loop seems strange to me. If you put any program artificially into an endless loop, you can kill it via "kill -9 <pid>". Have you tried that? The only exception I
can imagine is if there is a problem in the file system, like your elog logbooks are mounted via NFS or some other remote filesystem, and you have a problem there. Since the process might be stuck in kernel
mode, you cannot kill it. That's why I have all my servers running on local file systems. Just another thought.
/Stefan |
|
Re: Is it possible to only send an email based on the value of multiple attributes?, posted by Stefan Ritt on Mon Mar 9 17:24:42 2015
|
| Darren Hollinrake wrote: | My current setup notifies users if downtime = yes. Email Downtime Yes = user1@xyz.com, user2@xyz.com
Is it possible to only send an email based on the value of multiple attributes?
For my use:
user1 only needs notifications if Platform = Workstation and Downtime = Yes
user2 only needs notifications if Platform = Network and Downtime = Yes |
This is currently not implemented, but it's a good idea. I will keep it in mind for the next release. |
|
Re: Configure default time range in 'Find', posted by Stefan Ritt on Tue Mar 24 15:49:28 2015
|
Show last default = 0
always worked, even in my original code. It was just not documented. I added that.
| Andreas Luedeke wrote: |
|
Hi David,
I was confused because one normally does not need to include a line in the configuration to set a default value. A default is exactly what you get if you don't specify anything in the configuration  But I think I've figured it out: you were overriding the default in the global section for all logbooks and wanted to get back to the default for a particular logbook.
Then another simple solution would have been to remove the line in the global section and add it just in those logbook configurations, where you actually need it.
Anyway, it is good that one can now set the default in the configuration; I agree that this should always be possible.
Cheers
Andreas
| David Pilgram wrote: |
|
Hi Andreas,
Yes, the empty string does exactly that, in the drop down menu, but before my changes, I could not set it to be the default setting in the configuration file. In an archived logbook, it's perfectly possible for "all time" to be the only sensible value. I tried "Show last default = " and various other variants, with no success in getting what I actually required. Also, in the documentation, there was no mention of a way to set the default as "all time", just a list of number of days (week (7), month (31), year (364) etc), which also led me to believe that it was not possible with the existing code.
I've sent an email to Stefan giving my coding changes for information.
|
|
|
|
Re: Permission to view, posted by Stefan Ritt on Fri Mar 27 07:26:45 2015
|
You need
Password file = logbook.pwd
Login user = <name of allowed user(s)>
| Banata Wachid Ridwan wrote: |
|
I just read all administrator guide especially in :
http://midas.psi.ch/elog/config.html#access
and I didnt find it that exactly match with my need, or maybe I read wrong section :P
maybe my explanation little bit general.
I'll try to explain in detail, In my office, I just create 1 logbook for all employee,
one of my friend ask me if it possible to only give few people the ability to read all entry inside the logbook (all members), and the others (rest of the members) only able to input entry in the logbook and read their own.
please guide us.
| Andreas Luedeke wrote: |
|
Yes, it is possible. And explained in ELOG documentation.
| Banata Wachid Ridwan wrote: |
|
Hello,
related to the permission, is it possible to set permission ?, so only the owner or certain people can view list all logbok and regular member can only see their own logbook, not the others.
thanx for the help
|
|
|
|