ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
66718
|
Fri Feb 19 14:12:41 2010 |
| Tony Albers | tony.albers@gmail.com | Question | Linux | 2.6.3 | Re: Remove "demo" logbook.. |
Stefan Ritt wrote: |
Tony Albers wrote: |
Tony Albers wrote: |
Hi,
Is it possible to remove the "demo" logbook?
If I rename the section in elogd.cfg , it complains:
Error: logbook "demo" not defined in elog.conf Please use your browser's back button to go back
But there are other logbooks it can show instead. Is the "demo" logbook hardcoded in elogd?
/tony
|
I now upgraded to ver. 2.7.8, but I still cannot remove or disable the demo logbook.
|
The logbook name is in the URL of your browser. In the demo installation, there is a link in the start menu pointing to http://localhost:8080/demo. If you rename your logbook to something else, you have to change the URL accordingly. The simplest thing is to point it to http://localhost:8080, then you will be presented with a list of available logbooks.
|
Thanks Stefan, I managed to get it to work now. |
69495
|
Mon Mar 14 08:49:44 2022 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 3.1.3-7933898 | Re: Removal of ID and Date attributes |
Use the configuration option
List display = Day, Station Type, Start time UTC, ...
as written in the documentation.
Best,
Stefan
James Darrow wrote: |
Hello all,
I just found elog which is a great piece of software! I'm implementing it for use to log my shortwave listening contacts. The problem that I have is I'm moving over a current log to elog which already has a date of when the record was created, which is important.I renamed the old date to day to upload the log into elog. My problem is I don't need to see elog's ID# or date/time stamp of when the log was created seeing it's already in my data. My question is, is there any way to not show elog's ID# and date/time stamp or would I need to create a tab and if so could someone provide a config file where I could see how the tab was implemented. I've attached a screenshot of what it looks like so far. I've implemented the dark theme (which I like) that Anthoney had posted in the contibutions section.
Thanks in advance!
Jim
|
|
69496
|
Mon Mar 14 18:45:14 2022 |
| James Darrow | kb9mmc@ameritech.net | Question | Linux | 3.1.3-7933898 | Re: Removal of ID and Date attributes |
That worked! Thanks Stefan
Stefan Ritt wrote: |
Use the configuration option
List display = Day, Station Type, Start time UTC, ...
as written in the documentation.
Best,
Stefan
James Darrow wrote: |
Hello all,
I just found elog which is a great piece of software! I'm implementing it for use to log my shortwave listening contacts. The problem that I have is I'm moving over a current log to elog which already has a date of when the record was created, which is important.I renamed the old date to day to upload the log into elog. My problem is I don't need to see elog's ID# or date/time stamp of when the log was created seeing it's already in my data. My question is, is there any way to not show elog's ID# and date/time stamp or would I need to create a tab and if so could someone provide a config file where I could see how the tab was implemented. I've attached a screenshot of what it looks like so far. I've implemented the dark theme (which I like) that Anthoney had posted in the contibutions section.
Thanks in advance!
Jim
|
|
|
67893
|
Mon May 11 13:15:54 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 3.1 | Re: Remote entries with empty messages possible? |
The "command does not respond" means that the program starts reading in the main message text from the console. You can type several lines of text, and finish it off by hitting Ctrl-D (Ctrl-Z under Windows).
I see your point of having empty texts. Indeed the "" on the command line does not work presently, so you have to add a space as a workaround. I modified the elog code (committeed to bitbucket repository) to accept "" as empty text to suit your needs.
/Stefan
Edmund Hertle wrote: |
Hey,
I want to submit an entry to elog remotley using the "elog" command. For example:
elog -h elog-server-adress -l EO -a Fill=111
But this does not generate a new entry. Instead the terminal jumps to an empty new line and the command does not respond to any further inputs anymore (CTRL+C to get out). I have to add a message:
elog -h elog-server-adress -l EO -a Fill=111 "test"
also using an empty string does not work:
elog -h elog-server-adress -l EO -a Fill=111 ""
I could add a whitespace as a work-around, but I'm not sure if this is a bug or a feature.
To put this in some context: I want to create entries for certain measurements automatically, where all relevant parameters are already attribute fields. In the usual case the actual message will be empty but might be used if the operator wants to add a note after the meausrement has been done.
|
|
67895
|
Mon May 11 22:51:44 2015 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Linux | 3.1 | Re: Remote entries with empty messages possible? |
Hi Edmund,
Stefan already supplied a fix, but you could as well use a workaround: provide an empty file as text. The following works for Linux:
elog -h elog-server-adress -l EO -a Fill=111 -m /dev/null
Cheers
Andreas
Edmund Hertle wrote: |
Hey,
I want to submit an entry to elog remotley using the "elog" command. For example:
elog -h elog-server-adress -l EO -a Fill=111
But this does not generate a new entry. Instead the terminal jumps to an empty new line and the command does not respond to any further inputs anymore (CTRL+C to get out). I have to add a message:
elog -h elog-server-adress -l EO -a Fill=111 "test"
also using an empty string does not work:
elog -h elog-server-adress -l EO -a Fill=111 ""
I could add a whitespace as a work-around, but I'm not sure if this is a bug or a feature.
To put this in some context: I want to create entries for certain measurements automatically, where all relevant parameters are already attribute fields. In the usual case the actual message will be empty but might be used if the operator wants to add a note after the meausrement has been done.
|
|
852
|
Fri Dec 17 23:20:02 2004 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.5.5-2 | Re: Redirect to wrong hostname |
> I think you should be using tcp_hostname instead of gethostname if it is
> specified.
Sorry my late reply, I was ill for some time. I implemented your suggestion in
revision 1.522 which is available from CVS.
Note that there is also the "URL = xxx" option in the configuration file which
lets you specify the whole URL including the host name. |
856
|
Sun Dec 19 19:00:06 2004 |
| Ulrich Trüssel | ulrich.truessel@familienhund.ch | Bug report | Windows | 2.5.5-2 | Re: Redirect to wrong hostname |
know that illness... :-( but was the last of the family of 4 people
i'd like to ask for an other usefull change togehter with this and how url's are
handled by elog:
since there may be spaces in the name of a logbook (ex. "1stWordOfLogbook
2ndWordOfLogbook") it is very userfriendly to name logbooks. also it's easy th
make a reference for a other entry by copy and paste:
Display ThisURL = http://localhost:8080/$logbook/$message id
however, using spaces in the logbook name may give a wrong result, because the
url would be http://localhost:8080/1stWordOfLogbook
and the space as well as the 2ndWordOfLogbook//$message id is only normal text.
may it be possible stefan, to replace the space in an url (starting
with "http://") with a "+" or "%20"? this would allow to automate some things.
actual the logbook name has to be hardcoded.
> > I think you should be using tcp_hostname instead of gethostname if it is
> > specified.
>
> Sorry my late reply, I was ill for some time. I implemented your suggestion in
> revision 1.522 which is available from CVS.
>
> Note that there is also the "URL = xxx" option in the configuration file which
> lets you specify the whole URL including the host name. |
858
|
Mon Dec 20 17:18:16 2004 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.5.5-2 | Re: Redirect to wrong hostname |
Ok, I changed that in version 2.5.5-3. Note that one can also use the "elog:..."
substitution, like
Display ThisURL = elog:$logbook/$message id |