ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
2142
|
Mon Feb 19 20:46:39 2007 |
| bob | bobgrang@yahoo.fr | Question | Linux | Windows | V2.6.3-177 | Re: Required and {} |
Stefan Ritt wrote: |
bob wrote: | generally, can one handle "Required" and "{}" or "{ , }", ... |
For simple configuration files, that should work. If I have for example:
Attributes = Author, Type, Category, Subject
Options Type = Routine{r}, Software Installation{s}, Problem Fixed{p}, Configuration, Other
{r} Required Attributes = Author
Then the attributes "Author" is only required if "Type" equals "Routine". |
you are right, I try to re-examine my configuration and I will say to you |
2209
|
Tue Apr 24 11:00:56 2007 |
| bob | bobgrang@yahoo.fr | Question | Windows | All | last | Import log | Hi,
it is possible to import the file *.log of Elog towards another Elog?
thank you
Bob |
2211
|
Tue Apr 24 14:43:07 2007 |
| bob | bobgrang@yahoo.fr | Question | Windows | All | last | Re: Import log |
Stefan Ritt wrote: |
bob wrote: | Hi,
it is possible to import the file *.log of Elog towards another Elog?
thank you
Bob |
There are three methods:
- Copy over the *.log files from one Elog to the other. Make sure not to have entries with the same ID twice then.
- Set-up mirroring between two servers. This ensures a 1:1 copy of the server
- Export entries in CSV format (comma-separated-values) via 'Find', 'Mode = CSV', and do a 'CSV import' on the other side.
|
thank you,
but the last method (simplest for me) does not import the comment.
it's a pity... |
66990
|
Wed Jan 19 16:03:38 2011 |
| bob | bobgrang@gmail.com | Question | Windows | V2.8. | Modification aren't accepted | hello,
At home, when I change the config *. cfg, the modifications are not taken in consideration
Have you got a idea ?
Thanks a lot ! 
Bob |
66992
|
Wed Jan 19 16:19:56 2011 |
| bob | bobgrang@gmail.com | Question | Windows | V2.8. | Re: Modification aren't accepted |
Stefan Ritt wrote: |
bob wrote: |
hello,
At home, when I change the config *. cfg, the modifications are not taken in consideration
Have you got a idea ?
Thanks a lot ! 
Bob
|
Not really, you are the first one reporting this issue. Just some thoughts:
- Can you see the changes if you look at elogd.cfg with a text editor such as notepad?
- Some write protection of elogd.cfg
- Do you have more than one server running at the same time and changing the wrong one's config?
- Stefan
|
>- Can you see the changes if you look at elogd.cfg with a text editor such as notepad?
I change the configuration directly on elogd.cfg, (after i save and update my web page, and i not modification immediately)
>- Some write protection of elogd.cfg
no
- Do you have more than one server running at the same time and changing the wrong one's config?
i have one server with elog |
66996
|
Thu Jan 20 13:49:22 2011 |
| bob | bobgrang@gmail.com | Question | Windows | V2.8. | Re: Modification aren't accepted |
Stefan Ritt wrote: |
David Pilgram wrote: |
Let me report when I see this behaviour.
If I use a text editor on elog.cfg directly, while elog is running, then when I save the file, the new elog.cfg is in place,
but the running elog is still running with the old configuration. You have to restart elog for it to read the new config file and
use the new settings.
This does not apply if you edit elog.cfg via the "config" option in the menu command, where elog will read the new elog.cfg
just after it has been saved.
The reason I sometimes edit the file directly is if I want to create a new logbook, but with all the configuration of another logbook,
and it's quickest to cut-and-paste, change the heading, create a new directory and restart elog.
This may be completely off what is being reported.
|
Minor changes you do externally to the elogd.cfg file are reflected immediately under Windows (under Linux you have to send a HUP signal to the process to re-read the configuration). But if you make major changes like adding a new logbook, you have to restart elogd.
|
Yes, exactly!
I prefer to use the elog.cfg for change my config.
But, How do you do for restar the elogd ? with Unregister ELOG server service ?
Anyway, thanks for yours answers !
Bob
|
523
|
Thu Apr 8 15:05:43 2004 |
| Bertram Metz | bmetz@sbs.com | Question | Windows | 2.5.2 | Global password file together with guest account | Hello,
is it possible to have an guest account together with a global password file?
I tried to put the password file statement into the global section of
elogd.cfg. But in this case every user must login and it is not possible to
have a read only guest account.
But if I put the password file statemnet into the logbook sections, it is
possible to access the logbooks in read-only mode without logging in. The
drawback of this solution is, that you have to login into every logbook
seperately.
Bertram |
Attachment 1: elogd.cfg
|
[global]
Port = 8080
Logfile = elogd.log
Logging level = 3
Self register = 1
Logout to main = 1
Logbook tabs = 1
Password file = ./passwd
Admin user = BMetz
Guest menu commands = Back, Find, Login, Help
Guest find menu commands = Find, Select, Login, Help
[CP9]
;Password file = ./passwd
Theme = default
[CR9]
;Password file = ./passwd
Theme = default
|
525
|
Thu Apr 8 15:42:52 2004 |
| Bertram Metz | bmetz@sbs.com | Question | Windows | 2.5.2 | Re: Global password file together with guest account | > > Hello,
> >
> > is it possible to have an guest account together with a global password file?
> >
> > I tried to put the password file statement into the global section of
> > elogd.cfg. But in this case every user must login and it is not possible to
> > have a read only guest account.
> > But if I put the password file statemnet into the logbook sections, it is
> > possible to access the logbooks in read-only mode without logging in. The
> > drawback of this solution is, that you have to login into every logbook
> > seperately.
> >
> > Bertram
>
> Right, guest access is not possible with a global password file. This comes from
> the fact that people wish to protect their logbook selection page. What I can do
> is add another flag "protect selection page = 0 | 1". If "0", the logbook
> selection page can be seen without logging in. Is that what yo want?
>
> - Stefan
Yes, that is what I want.
Bertram |
|