Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 241 of 808  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Hide attachments  Show only new entries    6457 Entries 
Goto page Previous  1, 2, 3 ... 240, 241, 242 ... 806, 807, 808   Next  
ID Date Icondown Author Author Email Category OS ELOG Version Subject
  65991   Wed Oct 8 15:31:49 2008 Reply NeoNeo.X@web.deQuestionAll Re: Deny Wildcards

Stefan Ritt wrote:

 

Neo wrote:
Ist there a possibility to use wildcards specifiing the users who are allowed to use a command, like ... Allow New = admin1, admin2, admin3 Allow Edit = admin1, admin2, admin3 Deny New = * Deny Edit = *

 

 Wildcards are not implemented for that purpose. But a "Allow New = admin1, admin2" implicitly denies this command for all other users, I guess that's what you want. There is also the possibility to use "Guest Menu Commands" to allow everybody to read entries, but only logged in users to write and modify them.

 

I tried it in a global group configuration

[global monitoring]
Allow Edit = admin1, admin2
Allow New = admin1

But I as admin2 am still able to create new entries in the corresponding log books.

Is this configuration only for logbooks?

  65992   Wed Oct 8 21:37:32 2008 Reply Stefan Rittstefan.ritt@psi.chQuestionAll Re: Deny Wildcards

Neo wrote:

 

I tried it in a global group configuration

[global monitoring]
Allow Edit = admin1, admin2
Allow New = admin1

But I as admin2 am still able to create new entries in the corresponding log books.

Is this configuration only for logbooks?

 I just tried myself with following config:

[global]
port = 8080
password file = passwd
Allow New = joe

[demo1]
Theme = default
Attributes = Author, Subject

and it jus worked fine. When I'm not logged on as "joe", the "New" command even does not appear. If you would have supplied your correct ELOG version, I could have checked if you have an old version. In that case you could upgrade.

  65995   Mon Oct 13 10:37:27 2008 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.7.5-2130Re: Author field read only in new posts

 

Brassmann wrote:

Hi,

how can i make the author field read only on new postings? It should take the value from $long_name after login and without login there is no way to make new postings.

This is a part of my elogd.cfg


[global]
.......

Logfile = elogd.log
Logging level = 3
Login expiration = 24
Password file = ./passwd
.......

[Informations]
.......

Logout to main = 1
Logbook tabs = 1
Guest menu commands = Back, Find, Login, Help
Guest find menu commands = Find, Select, Login, Help


Preset Author = $long_name
Attributes = Author, Subject
Required Attributes = Author, Subject
........

Thanks Brassmann

 

 All you need is an addition

Locked Attributes = Author


  65996   Mon Oct 13 10:43:28 2008 Reply Brassmanninfo@flash-networx.deQuestionLinux2.7.5-2130Re: Author field read only in new posts

Stefan Ritt wrote:

 

Brassmann wrote:

Hi,

how can i make the author field read only on new postings? It should take the value from $long_name after login and without login there is no way to make new postings.

This is a part of my elogd.cfg


[global]
.......

Logfile = elogd.log
Logging level = 3
Login expiration = 24
Password file = ./passwd
.......

[Informations]
.......

Logout to main = 1
Logbook tabs = 1
Guest menu commands = Back, Find, Login, Help
Guest find menu commands = Find, Select, Login, Help


Preset Author = $long_name
Attributes = Author, Subject
Required Attributes = Author, Subject
........

Thanks Brassmann

 

 All you need is an addition

Locked Attributes = Author


 Thanks, works fine.

Regards Brassmann

  65997   Mon Oct 13 10:43:30 2008 Reply Brassmanninfo@flash-networx.deQuestionLinux2.7.5-2130Re: Author field read only in new posts

Stefan Ritt wrote:

 

Brassmann wrote:

Hi,

how can i make the author field read only on new postings? It should take the value from $long_name after login and without login there is no way to make new postings.

This is a part of my elogd.cfg


[global]
.......

Logfile = elogd.log
Logging level = 3
Login expiration = 24
Password file = ./passwd
.......

[Informations]
.......

Logout to main = 1
Logbook tabs = 1
Guest menu commands = Back, Find, Login, Help
Guest find menu commands = Find, Select, Login, Help


Preset Author = $long_name
Attributes = Author, Subject
Required Attributes = Author, Subject
........

Thanks Brassmann

 

 All you need is an addition

Locked Attributes = Author


 Thanks, works fine.

Regards Brassmann

  66005   Fri Oct 17 18:04:15 2008 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows Re: Easy way to submit images from screenshots as new entry

 

thorsten kamps wrote:

Hi, thanks for everyone involved for giving us the elog.

A question:

Is there an easy way (without intermediate save) to send screenshots (with irfan, snagit or hardcopy) as a new entry to an elog running on a remote machine?

Thanks, thorsten

 

 I use HoverSnap. This program generates a saved screenshot with one keystroke, so at least it saves you the manual save.

  66006   Fri Oct 17 18:06:04 2008 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows Re: Possible to submit entries by email to logbook

 

thorsten kamps wrote:

Hi, thanks to everyone involved for giving us the elog.

A question:

Is it possible to submit entries to an elog on a remote machine by email?

 

Thanks, Thorsten

 

 Have a look at Contributions.

  66010   Wed Oct 22 15:15:46 2008 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.7.5Re: Elogd crashes

 

soren poulsen wrote:

Hi

 I am experiencing trouble with Elog crashing. I think it crashes during input operations (new entries are being added).

Are there any preferred methods to troubleshoot this ? Any log files I could look at ?

For now, I let "monit" supervise the process and restart it if it crashes. But I would like to get to the root cause of the problem.

Soren Poulsen

CERN

 

Dear Soren,

sorry for the trouble, but it's very hard to diagnose this remotely. This forum here runs fine for many months, so in principle Elog should be stable (at least the current version 2.7.5). If you have an older version, please upgrade. If you have a way to reproduce the problem reliably, you can send me your config file and explain step-by-step how you make Elog crash. Then I can try to reproduce it here. Otherwise the only chance I see is to run elog from inside the debugger, and once it crashes record the stack trace and send it to me. If you don't know how to use the gnu debugger, I'm sure you find someone at CERN who knows. 

Best regards,

   Stefan

Goto page Previous  1, 2, 3 ... 240, 241, 242 ... 806, 807, 808   Next  
ELOG V3.1.5-3fb85fa6