Re: Email Notification (Not) Initiated by elog Client Utility, posted by Andreas Luedeke on Wed Jul 19 08:50:16 2017
|
Yes, parentheses in field content might be difficult to pass from a shell command. You did not even mention which Linux shell you are using and you did
not show the actual elog command. Maybe you want to add that information?
Phil |
|
Re: Weird behaviour of category filter, posted by Andreas Luedeke on Wed Jul 19 08:58:51 2017
|
Hi Daniel,
I agree: it should. And it does in my case; it works perfectly fine for my logbooks. Maybe you should have a closer look for special characters
in you configuration? Otherwise I don't know why it does not work for you. |
|
Re: Email Notification (Not) Initiated by elog Client Utility, posted by Phil Rubin on Wed Jul 19 08:59:52 2017
|
Thank you for responding.
I thought I provided the command at the end of the note:
/usr/local/bin/elog -h host -p port -l Notebook -u user passwd -a Author="Author" -a Type=Type -a Category=Category -a Subject="subject" |
|
Re: Email Notification (Not) Initiated by elog Client Utility, posted by Andreas Luedeke on Wed Jul 19 10:14:44 2017
|
If that is your command then it is obvious why no email is send:
you do set "Type=Type", but only for "Type=Problem(s)" and "Category=TDAQ" you would send an email.
Instead of writing "-h host" you should as well define the actual hostname, like "-h midas.psi.ch", likewise for all other |
|
Re: Email Notification (Not) Initiated by elog Client Utility, posted by Phil Rubin on Wed Jul 19 10:25:08 2017
|
I didn't realize you required every detail of the command, since the entry is being logged, but here is an example (only the user information is
blanked out):
/usr/local/bin/elog -h vmna62s1 -p 8080 -l NA62Logbook -u xxxx xxxx -a Author=Rubin -a Type=Problem\(s\) -a Category=Elog -a Subject="Client |
|
Re: Email Notification (Not) Initiated by elog Client Utility, posted by Andreas Luedeke on Wed Jul 19 13:37:33 2017
|
Okay, I can confirm that this does not work. It is likely related to the disclaimer in the ELOG documentation (https://midas.psi.ch/elog/config.html#conditional)
Conditional attributes are usually only used for change items in the entry form.
I guess that the "Email" command never worked with conditional attributes. I use the "Email" command and conditional attributes |
Password Protect Delete, posted by Michael Cianci on Thu Jul 20 18:38:20 2017
|
| We don't use a password file but would like to password protect (Admin only) the DELETE function in the MENU Thank You |
|
Re: Password Protect Delete, posted by Andreas Luedeke on Fri Jul 21 08:54:03 2017
|
You can allow guests to create entries, but only registered users (Admins) to delete (or edit) entries:
Menu commands = List, New, Edit, Reply, Delete, Find, Config, Logout,
Help |