| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
67497
|
Wed May 8 23:15:34 2013 |
 | Gian Henriques | gianlhsdm@gmail.com | Info | Windows | 292-2 | Re: Blockying user access |
| Gian Henriques wrote: |
|
| Garret Delaronde wrote: |
|
| Gian Henriques wrote: |
|
How can I block access to some tools (like edit, erase, config...) for each user? I want only admin users can edit, erase , etc.
I want know too, how can I erase configuration of SMTP? I make a test with the "elogd -t" command and now every time I create a new entry in my log book I receve the mensage of error to send email, cause I don't configure a SMTP host.
|
Hello, you can use the "Deny" flag in the config file for each logbook.
Deny <function> = <user>
Example: Deny Edit = Gian
simply add as many deny functions as you would like. Its a bit of work if you have a lot of logbooks but its the easiest solution.
Hope that helps.
Elog Syntax guide is helpful for this stuff too.
|
Thanks for help. It work's.
But I want to know if I can block a logbook from a user. For example I have a logbook named "Store". I want only users of the vendors have access to this log. How can I do it?
I didn't find this in manual.
|
The only way I find for this trouble is using the "Login user". But we have something best? |
|
67498
|
Fri May 10 17:21:50 2013 |
| Garret Delaronde | garret.delaronde@gmail.com | Info | Windows | 292-2 | Re: Blockying user access |
| Gian Henriques wrote: |
|
| Gian Henriques wrote: |
|
| Garret Delaronde wrote: |
|
| Gian Henriques wrote: |
|
How can I block access to some tools (like edit, erase, config...) for each user? I want only admin users can edit, erase , etc.
I want know too, how can I erase configuration of SMTP? I make a test with the "elogd -t" command and now every time I create a new entry in my log book I receve the mensage of error to send email, cause I don't configure a SMTP host.
|
Hello, you can use the "Deny" flag in the config file for each logbook.
Deny <function> = <user>
Example: Deny Edit = Gian
simply add as many deny functions as you would like. Its a bit of work if you have a lot of logbooks but its the easiest solution.
Hope that helps.
Elog Syntax guide is helpful for this stuff too.
|
Thanks for help. It work's.
But I want to know if I can block a logbook from a user. For example I have a logbook named "Store". I want only users of the vendors have access to this log. How can I do it?
I didn't find this in manual.
|
The only way I find for this trouble is using the "Login user". But we have something best?
|
I haven't found a specific way to block viewing a log book.
I use the top groups settings to keep users in the logbooks they only need access to.
Example
Top Group = Logbook Group1, Logbook Group 2
Group Logbook Group 1 = Logbook1, Logbook2
Group Logbook Group 2 = Logbook3, Logbook4
Then only assign users for logbook1 and logbook2 that you wish to view those logbooks only. They would have to go to the specific top group url in order to view the logbooks.
Then you can go to http://elogurl/(top group)/
And essentially just have the users view the only logbooks they are assigned to. |
|
470
|
Fri Feb 13 21:34:57 2004 |
| Stefan Ritt | stefan.ritt@psi.ch | | Linux | Windows | Mac OSX | ELOG V2.5.0 | Re: Behaviour of text when using "quote marks" in header fields |
Like this one ^^^ ???
I'm joking! I fixed the bug and updated the elogd server. Please find the new
version under CVS.
- Stefan |
|
472
|
Fri Feb 13 21:50:59 2004 |
 | Fergus Lynch | flynch@alternativenetworks.com | | Linux | Windows | Mac OSX | ELOG V2.5.0 | Re: Behaviour of text when using "quote marks" in header fields |
> Like this one ^^^ ???
>
> I'm joking! I fixed the bug and updated the elogd server. Please find the new
> version under CVS.
>
> - Stefan
Blimey! That was quick!
Many thanks for amending this. You'll be pleased to hear that my IT Operations
Team think this is the best thing since sliced bread...its going to replace a
blizzard of spreadsheets.
Cheers
Fergus |
|
1553
|
Thu Dec 15 17:33:39 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Other | Windows | 2.6.0 | Re: Bad date format. |
| Alex H wrote: |
[Liste]
Type Dernière image = Date
[Image Routeurs]
Type Derniere Image = Date
|
Maybe your additional accent. The attribute list contains Derniere Image, but in your first logbook you say Type Dernière image with accent grave, so this are not the same words. |
|
1554
|
Mon Dec 19 09:41:08 2005 |
 | Alex H | alex@synergie-inf.com | Other | Windows | 2.6.0 | Re: Bad date format. |
| Stefan Ritt wrote: |
| Alex H wrote: |
[Liste]
Type Dernière image = Date
[Image Routeurs]
Type Derniere Image = Date
|
Maybe your additional accent. The attribute list contains Derniere Image, but in your first logbook you say Type Dernière image with accent grave, so this are not the same words. |
It's work now !
Thanks  ! |
|
66701
|
Wed Feb 3 09:49:58 2010 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | V2.7.5-213 | Re: Backing up an entire eLog |
| Ed Rogers wrote: |
|
Hi, I've been using the ELOG software for about a year now. I love it! But as my ELOG becomes more valuable, I become more paranoid about potential data loss. (We've had numerous close-calls with disk failures, recently.) Is there a way to download a backup of my ELOG, all at once? Maybe a command that could create a tar.gz of all the entries and attachments? Further, is there also a command to restore from such a backup? Apologies if this question is answered elsewhere. I couldn't readily find it in the documentation. Regards, --Ed
|
There is a simple way. In your logbook directory you will find files of the format xxyyzza.log where xxyyzz is the year/month/day of the entries being submitted during that day. The attachments have a similar form, they have just the attachment name appended to the date. To back it up, just copy or tar all files of that directory. If you want to back up a certain year, you can select 2009 for example with 09*.* To restore these files, simply untar them into the directory and restart the elogd daemon. The restart is necessary, since during start the daemon indexes all entries. |
|
628
|
Wed Jul 28 21:39:21 2004 |
 | Stefan Ritt | stefan.ritt@psi.ch | Bug report | All | 2.5.3 | Re: BUG?: Preset text = causes replication of text when re-editing a logbook entry. |
> With the "Preset text = " specified, when re-editing a logbook entry (say to
> correct a spelling error) the text of the "Message" is replicated and placed
> directly below the original text.
That should be fixed since revision 1.370 from Jul 7th, 2004. Please update. |