Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 790 of 796  Not logged in ELOG logo
ID Date Icon Author Author Email Categoryup OS ELOG Version Subject
  69001   Thu Aug 15 13:34:23 2019 Reply Andreas Luedekeandreas.luedeke@psi.chRequestLinux3.1.4Re: restrict edit time

Yes, I agree that cleaning up old Draft entries and correcting/deleting old entries is a job for the administrator. Currently I do what you've said: commenting out "restrict edit time", changing the entry, commenting in "restrict edit time".

There are already some commands specifically for the admin:

  • Admin textarea = <cols>,<rows>
  • Admin user = <user list>

It would make sense to add more of them, for this specific case:

  • Admin restrict edit time = <hours>

If that is set to "-1", then the Admin can edit old entries regardless of their age. Actually there is no option to "unset" restrict edit time inherited from a global config: a negative time would make sense as "disabling" restrict edit time.

Another item for the endless wishlist ;-)

Cheers, Andreas

Sebastian Schenk wrote:

Hello,
I have experienced some inconveniences with the restrict edit time option.

First, it is not possible for admin users to edit an entry after the edit time.
The restrict edit option allows admin users to edit posts from other users,
so I think admins should also be allowed to edit posts after edit time.
As they can edit the config and temporarily disable the restrict edit time option, which is an issue.

Secondly, if a user made a draft and did not submitted it before the edit time runs out,
the draft got stuck as it cannot be edited (and submitted) any more.

Best wishes,
Sebastian

 

  69057   Sat Nov 9 22:44:23 2019 Idea paveltemp213@gorodok.netRequestAll3.1.4Subdirectories in logbooks

Hello, Is there any way to organize logbooks in some kind of tree with sublogbooks or just have a subdirectories in a logbook directory on the filesystem (treat it as a sublogbook if its name is different from 4 digits of year and pin above all the entries in a list) to structure entires a bit?

 

  69058   Mon Nov 11 13:09:35 2019 Reply Stefan Rittstefan.ritt@psi.chRequestAll3.1.4Re: Subdirectories in logbooks

Just use groups as written in the manual: https://elog.psi.ch/elog/config.html#groups

Stefan

pavel wrote:

Hello, Is there any way to organize logbooks in some kind of tree with sublogbooks or just have a subdirectories in a logbook directory on the filesystem (treat it as a sublogbook if its name is different from 4 digits of year and pin above all the entries in a list) to structure entires a bit?

 

 

  69064   Sun Nov 24 20:29:24 2019 Question Frank Baptistacaffeinejazz@gmail.comRequestMac OSX3.1.3-fd7f1e2Executing a shell command using elogd Windows service

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

  69065   Sun Nov 24 21:10:28 2019 Reply Frank Baptistacaffeinejazz@gmail.comRequestWindows3.1.3-fd7f1e2Re: Executing a shell command using elogd Windows service

Sorry -- I somehow selected the wrong OS in my original message. Asleep at the wheel again.

Frank Baptista wrote:

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

 

  69067   Mon Nov 25 16:32:07 2019 Reply Stefan Rittstefan.ritt@psi.chRequestWindows3.1.3-fd7f1e2Re: Executing a shell command using elogd Windows service

Wow, having these color signal lamps really looke like a cute solution, made me laugh.

No, there is no other way than the Execute new thing. I have given up long time ago to use Windows services, because they are very hard to debug and very limited. So at our site everything runs under Linux.

Have you tried to specify the explicit path of your log file? Like Execute new = echo $Status > C:\Path\Last_status.log

Best,
Stefan

Frank Baptista wrote:

Sorry -- I somehow selected the wrong OS in my original message. Asleep at the wheel again.

Frank Baptista wrote:

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

 

 

  69069   Sat Nov 30 15:46:16 2019 Reply Frank Baptistacaffeinejazz@gmail.comRequestWindows3.1.3-fd7f1e2Re: Executing a shell command using elogd Windows service

Well, there I was, eating Thanksgiving dinner, when suddenly, it hit me (no, not indigestion).  I can write a simple program that parses out the latest "Status" from the most recent logbook file -- a relatively easy task, since it's a text file.  This solution avoids having to execute a shell command at all.  GOOOOOOAAAAAAL!!! smiley

As always, I appreciate all your help...can't thank you enough!

All the best,
Frank

Stefan Ritt wrote:

Wow, having these color signal lamps really looke like a cute solution, made me laugh.

No, there is no other way than the Execute new thing. I have given up long time ago to use Windows services, because they are very hard to debug and very limited. So at our site everything runs under Linux.

Have you tried to specify the explicit path of your log file? Like Execute new = echo $Status > C:\Path\Last_status.log

Best,
Stefan

Frank Baptista wrote:

Sorry -- I somehow selected the wrong OS in my original message. Asleep at the wheel again.

Frank Baptista wrote:

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

 

 

 

  69080   Wed Jan 22 16:10:51 2020 Question Daniel Pfuhldaniel.pfuhl@medizin.uni-leipzig.deRequestLinux | Windows | Mac OSX | All | Other3.1.4CSS for HTML Mails

Hi there,

we extensively use Logbuch as a change documentation platform.

E-Mail notifications for new entries are very important for us.

Since we store sensible data in our logbooks the server is protected by a firewall.

After the firewall was activated the HTML mails are not rendered by the Outlook Mail clients we use - when they are located in an "external" net behind the firewall. I assume that's because of the css stylesheet which is linked in the source code of the HTML mail.

Is there any chance to include the CSS information in the HTML code? Otherwise we would need to make the CSS accessable from anywhere which requires in turn that the path of the CSS file can be customized.

Any idea how to solved this issue?

Best regards,

daniel

ELOG V3.1.5-2eba886