Expand TEXT colum in Summary view?, posted by dale cooper on Mon Aug 18 10:56:05 2008
|
Hello All,
I am wondering if it is possible to configure ELOG to expand the TEXT column in the SUMMARY view? As it stands I get about 48 characters displayed per line in the in the TEXT column, with 3 lines getting displayed per ENTRY (approximately 144 characters per ENTRY). So what I'd like to do is see if it is possible to EXPAND the TEXT column in the SUMMARY view to allow say.... 100 characters per line, or say 275 characters per ENTRY when viewing the SUMMARY view?
Is this possible? If so, how does one go about doing this... I tried to search the site thoroughly before posting my question, I just didn't see it mentioned anywhere... Help please =)
Thanks!
agentdcooper |
|
Exim4, posted by Matthew D. on Tue Apr 23 22:14:42 2013
|
Hi,
My email configuration is a little complicated as all emails must be relayed to a central server with TLS authentication.
So far I've been unable to get the ELOG to work with email, after numerous attempts . I have got exim4 working on this machine but I don't understand how the elog sends emails well enough, to configure it to recognise and use exim4. Setting localhost/ my domain/ IP (and variations) under 'smtp host' doesn't work. (cannot connect to server)
The most interesting error I have been able to get is:
"AUTH command used when not advertised"
or
"Unrecognized authentication type"
Any advice?
|
Executing a shell command using elogd Windows service, posted by Frank Baptista on Sun Nov 24 20:29:24 2019 
|
Greetings!
We've been successfully running nearly a dozen separate logbooks on independent laptops -- all of them are running elogd as a Windows service. This works well, since I've also set up auto recovery options in the event that the service inadvertently stops.
Now, I have a need to place the value of an attribute of the latest log entry into a basic text file. Of course, this works just fine if I have launched elogd -x as a normal executable, using Execute new = echo $Status > Last_status.log in my CFG file. However, I would like to be able to do this using the Windows service which is running in the background.
Is there another way to write the value of an attribute into a separate file? If not, do I have to have a special build of ELOG in order to be able to enable the Windows service to execute shell commands? For the record, these logbooks are running on secure laptops that are isolated onto their own network, and the user is unable to edit the CFG file.
In case you're wondering about the reason for the separate text file -- I've written a separate program which illuminates one of 4 different color signal lamps (mounted on a test station), based on the latest "Status" of the test station. (Running, Idle, Broken, Other).
I appreciate any guidance here -- this is a "big deal" here, as one glance over the floor gives us an idea of what's running (or not).
Thanks!
Frank |
Execute new|edit doesn't seem to work, posted by Juergen Diefenbach on Fri Feb 26 17:35:54 2016
|
I am trying to use the "Execute new|edit|delete" feature to track changes to an elog using git.
When a new entry is created a shell script should be executed (certain attributes of the logbook entry should be passed as arguments to it). The script will then automatically stage all changes and create an appropriate git commit message. For a "new" entry in the logbook the commit message is a bit more verbose. When editing or deleting a message only a short commit message like "Edit message 25" should be created. Therefore I really need to distinguish between "new", "edit", and "delete".
However, I experienced unreproducible behavior when creating "new" entries. Sometimes the command specified by "Execute new=" is called, sometimes the one specified by "Execute edit=" is executed. Most of the time it doesn't work as expected. 
What I did so far to understand what goes wrong is I looked into elogd.c and found invoid submit_elog(LOGBOOK * lbs) that bedit is sometimes true and sometimes false, when creating a new entry, although it should be false then (right?).
This is why elogd then sometimes retrieves the wrong shell command from getcfg(lbs->name, "Execute edit"...) instead of getcfg(lbs->name, "Execute new"...) around line 23610 (not exact due to some eprintf()s inserted here and there to look at bedit and so on).
When deleting an entry, everything works fine: the shell command defined via "Execute delete=" is run, but this happens somewhere else in the code so it's not a surprise.
Do you have an idea how to fix this or can you point me in some direction to further track it down? Thank you! |
|
Execute attribute, posted by Alan Grant on Fri May 10 04:34:36 2019
|
Apart from an inline shell command that can be run with the Execute attribute, is it possible to run an external script file? I would like to run a Powershell script with the Elog attribute data parameters passed to it upon Submit New entry. |
|
Execute a python command?, posted by harley on Tue Nov 9 19:28:53 2010
|
Is there a way to add a button to the elog interface which would execute a python command? |
Example scripts how to migrate or combine logbooks, posted by Roger Kalt on Mon Nov 18 16:58:21 2019
|
Attached the shell scripts using awk and sed how I have migrated two separated logbooks into one single and how I re-adjusted certain attributes. |
|
Escape emoticons in ELCODE, posted by Gernot Buselmeier on Fri Mar 20 14:33:53 2009
|
Hi,
I want to write a text like "John:Doe" in ELCODE. However the ":D" is converted to a LOL emoticon. I tried various ways to escape this. One solution I found was entering "John\:Doe". However, the upper-case D is converted to lower-case: the result reads "John:doe".
Thanks for an answer and many thanks for providing ELOG.
Gernot |