ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
68301
|
Mon Apr 4 14:09:42 2016 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | v3.1.1 | Re: Send email based on lookup of an attribute | > I'm trying to send an email based on an attribute, in other words, a lookup and not $user_email of the author.
>
> For instance, if I set a an attribute "Assignee" with a valid user full name (i.e. John Smith), I'd like to look up John Smith's
> email address from the password file and send him an email. I can't seem to find it something like that in the docs, I can write
> a script to do that, but was looking for a less cumbersom way of doing it. Thanks in advance.
Unfortunately such a feature is not implemented in the current version.
Stefan |
68307
|
Wed Apr 27 14:39:28 2016 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | All | V3.1.1 | Re: How to enforce line breaks in plain text entries? | > > We use ELOG for our accelerator operation logbooks. As part of the shift handover every shift prints out all
> > entries made during the shift and files the printouts. If one entry in the shift was plain text without
> > appropriate linebreaks (like this one), then this screws up the printout: the whole window is scaled to the
> > width of this line and either the printout is cut off at the right side, or the whole content is scaled down to
> > very tiny scale, which makes it unreadable.
> >
> > Is there a way to enforce line breaks in plain text entries?
>
> Obviously there is: this logbook does add line breaks?!?
>
> Maybe it is only a problem with entries made by the "elog" command?
> I'll find it out and re-post.
>
> Cheers
> Andreas
Yepp, this is a (missing) feature of the elog command. Can you pre-process your messages outside of it, or do I have to add code to elog to do that?
Stefan |
68312
|
Fri Apr 29 11:45:51 2016 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.8 | Re: How to delete a logbook? | Deleting a logbook in the config page (via "Delete this logbook") only removes the logbook defiition from the config file. To really erase all information you have to go to the file system and delete the whole directory belonging to that logbook. You have one subdirectory per year, containing all logobok entries and also attachments, so make sure you do a recursiver directory removal.
Stefan
steve bray wrote: |
Hello,
What is the procedure to delete a logbook (incl. attachments)?
Steve
|
|
68334
|
Tue Jun 14 14:33:40 2016 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 3.1.1 | Re: cannot use "use email heading" | The setting
Use Email Heading
is only used for plain text encoding of email messages. The default is HTML encoding, which has its own heading which cannot be changed. If you want the different heading, use
Email encoding = 1
and you get it.
/Stefan
utomoadji wisnubroto wrote: |
Hello,
i have config file elogd.cfg like below:
[Tom Yaht]
Theme = default
;Comment and Tittle
Comment = LogBook
Page title = Tom LogBook
List page title = Tom LogBook
;admin and user settings
admin user = tom
login user = tom, soc
login expiration = 2
Restrict edit time = 8
Attributes = Controllers, Event Date/Time, Site, Engineers, Type, Category, Subsystems, Subject, Distribution-Mail, EMail to
Moptions Distribution-Mail = Controllers, Engineers, Consultant Team, Manager
;Email settings
Email Distribution-Mail "Controllers" = ble@xxx.com, cor@xxx.com, nor@xxx.com
Email Distribution-Mail "Engineers" = blo@xxx.com, sur@xxx.com, ars@xxx.com
Email Distribution-Mail "Consultant Team" = bli@xxx.com, zam@xxx.com
Email Distribution-Mail "Manager" = bos@xxx.com
Email all = $EMail to
Use Email Subject = Tom Logbook - $Subject
Use Email Heading = New Tom Logbook entry
Use Email Heading edit = Tom Logbook has been updated
The Subject successfully displayed as i expected , but the email heading still use default heading "A new ELOG entry has been submitted" , while i want to changeit to be "New Tom Logbook entry" as i mention in Use Email Heading above.
Could anybody help me.
Thank you
|
|
68336
|
Tue Jun 14 17:01:04 2016 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 3.1.1 | Re: Guest menu commands not working as advertisted | There are two menus, one for the list display, and one for the individual entry display. To change the first, you need
List menu commands = ...
Guest list menu commands = ...
Greg Christian wrote: |
Hello,
I am trying to set up my elog to have read-only guest access and require registration/password for users to be able to post to the elog. I've tried following the instructions here: https://midas.psi.ch/elog/faq.html#6, i.e. putting the following lines under the [global] section of my elogd.cfg file:
Menu commands = List, New, Edit, Reply, Duplicate, Find, Config, Logout, Help
Guest menu commands = List, Find, Login, Help
When I do this, I do get guest acccess, however the menu items are
New | Find | Select | Import | Config | Logout | Last day | Help
rather than the List, Find, Login, Help I would expect. Also, if I click on Logout, it simply does nothing, which means there's now no way to log in as a registered user.
Any thoughts on what might be wrong?
Thanks,
Greg
|
|
68339
|
Tue Jun 21 16:33:56 2016 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Mac OSX | 3.1.0 | Re: pdf thumbnails in latest Imagemagick | Hi John,
I use ImageMagick 6.9.3-10 on my Mac OSX 10.11.5 and it works fine. So apparently the parameters of the ImageMagick program have been changed. If you set the logging level to 2 or higher, you should see the "convert" and "identify" commands in the logging file. If you try these commands manually from the command line, you will see if they succeed or give an error. Please post this error here so I can have a look.
Cheers,
Stefan
John Haggerty wrote: |
I think with the latest Imagemagick from brew (6.9.4-7) that pdf thumnails no longer get made; the attachment is there but the message "Cannot create thumbnail, please check ImageMagick installation" apears instead of the thumbnails. I couldn't make out from elogd -v 3 why they failed, but I couldn't make out the exact convert command that was failing. This is on MacOS 10.11.5 and I think the updated version ofImagemagick was the last thing that changed before it failed.
|
|
68342
|
Mon Jun 27 16:06:55 2016 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.9.2 | Re: Unable to set a custom logbook dir on Debian 8 from the repository package | The debian version of elog is pretty old with quite a number of bugs fixed in meantime. Unfortunatlely the debig packase has not bee updated by the maintainers. So better download the current version from bitbucket and compile elogd yourself.
S. Caiazza wrote: |
Dear all
I installed elog from the current stable repository on Debian 8 (jessie)
The installation went on smoothly, I modified the configuration files of the Apache server as described in the manual to use the elog in parallel with an existing webserver and then I tested. The demo logbook loads fine and I see that elog created a folder for the logbook in /var/lib/elog/logbooks, which is the directory specified by default in the /etc/init.d/elog file.
Then I modified the /etc/elog.conf file, added the following lines in the global section (custompath is a local path)
Resource dir = /<custompath>/elog/res
Logbook dir = /<custompath>/elog/logbooks
And I created a new logbook.
After restarting the elog service the second database is correctly created but both of them are still stored in /var/lib/elog/logbooks so it seems the global configurations in the config file are overwritten.
How can I specify the custom folder so that the new logbooks are written there?
|
|
68345
|
Wed Jun 29 16:58:15 2016 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Linux | Windows | Mac OSX | All | Other | ELOG V3.1.1 | Re: More than 100 attributes | The limit is in the variable
#define MAX_N_ATTR 100
in elogd.c. If you increase it and recompile, it could work, but at some time you will get a stack overflow since arrays with that size are dynamically allocated on the stack, and depending on your compiler settings the stack size is only finite.
Stefan
JD wrote: |
I am modifying the elogd.cfg automatically with a script. The Script fetches a list of systems from a LDAP database and writes them into an "Options" line in the elog.cfg.
Everything worked fine, until we hit the critical number of 100 attributes. I saw this is also stated in the manual.
Is there any workaround? I downloaded the source code and hat a quit look, but couldn't find the section which is responsible for this behavior.
Is there a reason for this limit?
Thanks
Jonathan
|
|
|