Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 148 of 806  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Show attachments  Show only new entries    6447 Entries 
Goto page Previous  1, 2, 3 ... 147, 148, 149 ... 804, 805, 806   Next  
ID Date Icon Author Author Email Category OS ELOG Version Subject
  68651   Sun Jul 30 07:39:23 2017 Question Gerardo Abihagglegabihaggle@gmail.comQuestionWindows3.1.3-fd7Enable LDAP on Windows

Hi All,

I'm running ELOG on a Windows machine and I would like to use LDAP for Authentication, however to achive this I need to compile elog. Any advice on how to do that on Windows?

Thanks!

  68650   Mon Jul 24 14:33:51 2017 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionWindowsLatestRe: Conditional attribute activation

Yes, this is possible by using "Conditional Attributes". Have a look at the ELOG syntax help: https://midas.psi.ch/elog/config.html#conditional

To hide attributes on edit, you can use "Show Attributes Edit =  ..." for the conditions; and you only list the comment reason for the case where the value of the other attribute has the value "reserved".

If you don't get it to work, then just post your logbook config with some comments on what you want to achieve.

Cheers, Andreas

Devrim Esenturk wrote:

I have a stock database running latest elog version on windows. I am reserving some products which not been sent to customer mistakenly and using value "reserved" for it. But I need another attribute for comment reason of reserving but this attribute must be activated when reserved value selected. Is this possible? I didn't see any option for this at admin guide.

 

Thank you

 

  68649   Fri Jul 21 15:24:33 2017 Question Devrim Esenturkdevrim.esenturk@gmail.comQuestionWindowsLatestConditional attribute activation

I have a stock database running latest elog version on windows. I am reserving some products which not been sent to customer mistakenly and using value "reserved" for it. But I need another attribute for comment reason of reserving but this attribute must be activated when reserved value selected. Is this possible? I didn't see any option for this at admin guide.

 

Thank you

  68648   Fri Jul 21 08:54:03 2017 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionWindowsv2 9.2-2475Re: Password Protect Delete

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
Guest menu commands = List, New, Reply, Find, Login, Help

See https://midas.psi.ch/elog/config.html#general for details.

Michael Cianci wrote:

We don't use a password file but would like to password protect (Admin only) the DELETE function in the MENU     Thank You

 

  68647   Thu Jul 20 18:38:20 2017 Question Michael Ciancimcianci@lhs.orgQuestionWindowsv2 9.2-2475Password Protect Delete

We don't use a password file but would like to password protect (Admin only) the DELETE function in the MENU     Thank You

  68646   Wed Jul 19 13:37:33 2017 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionLinux3.1.3Re: Email Notification (Not) Initiated by elog Client Utility

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 extensively, but I've never tried before to use "Email" in a condition.

I've tested the functionality with the following minimal configuration for the latest ELOG version 3.1.3-aded4ae :

Attributes = A, B
Options A = X{1}, Y{2}
Options B = N, M
{2} Email B M = andreas.luedeke@psi.ch

The following elog command creates the desired entry, but does not send out an email. Creating the identical entry via the web form does initiate the email.

elog -u <user> <password> -h <host> -p 80 -l <logbook> -a "A=Y" -a "B=M" -n 1 "entry by elog cmd"

Thank you Phil for pointing out the problem.

Cheers, Andreas

Phil Rubin wrote:

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 Initiated E-mail Notification" "Tests"

From elogd.cfg:

Options Type = Routine{1}, Problem(s){2}, Other{3}
Options Category = Access, Beam, CHANTI, CHOD, Computer/Network, DCS/DSS, Elog, 
GTK, HASC, IRC/SAC, KTAG, LAV, LKr, MUV, NewCHOD, Online Monitor, RICH, Run, Run
 Control, Shift, STRAW, TDAQ

{1} Email Category Elog =
{2} Email Category Elog = Philip.Rubin@cern.ch
{3} Email Category Elog =
 

The TDAQ-category command that is misbehaving is essentially identical:

/usr/local/bin/elog -h vmna62s1 -p 8080 -l NA62Logbook -u xxxx xxxx -a Author="Run Control" -a Type=Problem\(s\) -a Category=TDAQ -a Subject="Board Reload" "KTAG4"

 

Andreas Luedeke wrote:

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 parameter.

Phil Rubin wrote:

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" "text"

This results in an entry being appropriately logged in Notebook with the correct author, type, category, subject, and text.  The only problem is that, when the type is such that email notification should be sent to the list associated with category, it is not sent.

For the record, I reconfigured elogd.conf so that parentheses are no longer there, but this made no difference, so this isn't the problem.

Sorry for forgetting these details:  bash shell; linus version 2.6.32-696.el6.x86_64

 

Andreas Luedeke wrote:

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 Rubin wrote:

Our configuration sends out e-mail notifications based on a hierarchy of attributes, and works fine with WEB submissions, but not with client utility submissions (no notifications are sent; the log doesn't show it even trying to send any: 14-Jul-2017 18:36:01 [rubinp@nn.nn.nn.nn] {Notebook} NEW entry #0) .  Since notification is the default (suppression requires -x), I presume there is something wrong with the way we're going about this.  Can you see what it is?  Could it be the parentheses in the type Problem(s), which have to be sent at the shell in the client command as Type=Problem\(s\)?

[global]

.

Suppress Email to users = 1
.

 

[Notebook]

.

Attributes = Author, Type, Category, Subject
Options Type = Routine{1}, Problem(s){2}, Other{3}
Options Category = ... TDAQ ...

.

{1} Email Category TDAQ =
{2} Email Category TDAQ = user1@aa.bb, user2@cc.dd,...

{3} Email Category TDAQ =
.

Use Email Subject = Elog Notice: $subject
 

Command:  /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" "text"

 

 

 

 

 

  68645   Wed Jul 19 10:25:08 2017 Reply Phil Rubinrubinp@cern.chQuestionLinux2.9.2Re: Email Notification (Not) Initiated by elog Client Utility

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 Initiated E-mail Notification" "Tests"

From elogd.cfg:

Options Type = Routine{1}, Problem(s){2}, Other{3}
Options Category = Access, Beam, CHANTI, CHOD, Computer/Network, DCS/DSS, Elog, 
GTK, HASC, IRC/SAC, KTAG, LAV, LKr, MUV, NewCHOD, Online Monitor, RICH, Run, Run
 Control, Shift, STRAW, TDAQ

{1} Email Category Elog =
{2} Email Category Elog = Philip.Rubin@cern.ch
{3} Email Category Elog =
 

The TDAQ-category command that is misbehaving is essentially identical:

/usr/local/bin/elog -h vmna62s1 -p 8080 -l NA62Logbook -u xxxx xxxx -a Author="Run Control" -a Type=Problem\(s\) -a Category=TDAQ -a Subject="Board Reload" "KTAG4"

 

Andreas Luedeke wrote:

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 parameter.

Phil Rubin wrote:

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" "text"

This results in an entry being appropriately logged in Notebook with the correct author, type, category, subject, and text.  The only problem is that, when the type is such that email notification should be sent to the list associated with category, it is not sent.

For the record, I reconfigured elogd.conf so that parentheses are no longer there, but this made no difference, so this isn't the problem.

Sorry for forgetting these details:  bash shell; linus version 2.6.32-696.el6.x86_64

 

Andreas Luedeke wrote:

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 Rubin wrote:

Our configuration sends out e-mail notifications based on a hierarchy of attributes, and works fine with WEB submissions, but not with client utility submissions (no notifications are sent; the log doesn't show it even trying to send any: 14-Jul-2017 18:36:01 [rubinp@nn.nn.nn.nn] {Notebook} NEW entry #0) .  Since notification is the default (suppression requires -x), I presume there is something wrong with the way we're going about this.  Can you see what it is?  Could it be the parentheses in the type Problem(s), which have to be sent at the shell in the client command as Type=Problem\(s\)?

[global]

.

Suppress Email to users = 1
.

 

[Notebook]

.

Attributes = Author, Type, Category, Subject
Options Type = Routine{1}, Problem(s){2}, Other{3}
Options Category = ... TDAQ ...

.

{1} Email Category TDAQ =
{2} Email Category TDAQ = user1@aa.bb, user2@cc.dd,...

{3} Email Category TDAQ =
.

Use Email Subject = Elog Notice: $subject
 

Command:  /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" "text"

 

 

 

 

  68644   Wed Jul 19 10:14:44 2017 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionLinux2.9.2Re: Email Notification (Not) Initiated by elog Client Utility

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 parameter.

Phil Rubin wrote:

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" "text"

This results in an entry being appropriately logged in Notebook with the correct author, type, category, subject, and text.  The only problem is that, when the type is such that email notification should be sent to the list associated with category, it is not sent.

For the record, I reconfigured elogd.conf so that parentheses are no longer there, but this made no difference, so this isn't the problem.

Sorry for forgetting these details:  bash shell; linus version 2.6.32-696.el6.x86_64

 

Andreas Luedeke wrote:

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 Rubin wrote:

Our configuration sends out e-mail notifications based on a hierarchy of attributes, and works fine with WEB submissions, but not with client utility submissions (no notifications are sent; the log doesn't show it even trying to send any: 14-Jul-2017 18:36:01 [rubinp@nn.nn.nn.nn] {Notebook} NEW entry #0) .  Since notification is the default (suppression requires -x), I presume there is something wrong with the way we're going about this.  Can you see what it is?  Could it be the parentheses in the type Problem(s), which have to be sent at the shell in the client command as Type=Problem\(s\)?

[global]

.

Suppress Email to users = 1
.

 

[Notebook]

.

Attributes = Author, Type, Category, Subject
Options Type = Routine{1}, Problem(s){2}, Other{3}
Options Category = ... TDAQ ...

.

{1} Email Category TDAQ =
{2} Email Category TDAQ = user1@aa.bb, user2@cc.dd,...

{3} Email Category TDAQ =
.

Use Email Subject = Elog Notice: $subject
 

Command:  /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" "text"

 

 

 

Goto page Previous  1, 2, 3 ... 147, 148, 149 ... 804, 805, 806   Next  
ELOG V3.1.5-3fb85fa6