| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1281
|
Wed Jul 20 20:13:26 2005 |
 | Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.5.4-3 | Re: Cannot stat() config file |
| Stefan Rudat wrote: | | Cannot stat() config file; No such file or directory. |
I do not know what exactly is going on. This error occurs during runtime when elog tries to check if the config file (usually elogd.cfg) has changed. It checks if the file is there on startup, but apparently it is there, otherwise elog would not start. Then it checks about once per second if the file access time has changed. If so, it rereads the file. This way changes to the file become valid immediately, without restarting elog. The fact that elog has access to the file on startup, but not later, is somehow strange. Maybe you lock this file with an editor, or it is on a network drive which gets disconnected, or the permission changed after the startup. Something in that direction. |
|
1280
|
Wed Jul 20 19:49:21 2005 |
 | Juliana Peng | jpeng@yorku.ca | Request | Linux | V2.6.0 | hide attributes when view the logbook | Hi Stefan,
Thanks for the great work. We have been using elog for a year as inventory management.
Now we have a long list of attributes in our logbook, some of those we want to keep in database for record, but we don't want to see them because they are not used very often. I tried the "Show Attributes". my conf is like this:
Attributes = Name, SysAdmin, OS, Manufacturer, Model, Serial Number, Description, Main Function, Location, Memory, CPU Speed, Num CPU, Owner, Contact Name, Contact Phone, Contact Email, Bought From, Bought Date, Maintenance, Network Drop, Console Drop
.
.
.
Options OS = SunOs{1}, Linux{2}, Aix
{1} Show Attributes = Name, SysAdmin, OS, Manufacturer, Model, Serial Number, Description
but it seems only effective when adding the new entry. All the attributes will show in logbook. Is there a way to hide some of the attributes? It would be good to let each user to choose what to see what not to see, create their own view. Can you put it on your to-do list or wishlist?
Thanks |
|
1279
|
Wed Jul 20 08:32:06 2005 |
 | Stefan Rudat | sr@smartnd.com | Question | Windows | 2.5.4-3 | Cannot stat() config file | Hi
Elog runs now for serveral month without any problem at a Windows 2000 server.
I must change the access rights for all Folders, remove the user everyone and set the
Rights only to defined groups .
Now I can see following Event ID
Event Type: Information
Event Source: ELOG
Event Category: None
Event ID: 0
Date: 20.07.2005
Time: 08:14:24
User: N/A
Computer: SNDSRV1
Description:
The description for Event ID ( 0 ) in Source ( ELOG ) cannot be found.
The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: Cannot stat() config file; No such file or directory.
My question now. Have someone see the same Problem ?
It this is a access right problem How to set up the access rights for Elog
Elog folders ?
Bye |
|
1278
|
Mon Jul 18 18:36:32 2005 |
 | Emiliano Gabrielli | AlberT@SuperAlberT.it | Bug report | Linux | rev 1.703 | Re: Display Subject and HTML tags, regression |
| Emiliano Gabrielli wrote: | rev 1.703 makes the following code not to work:
Display Subject = <b>$subject</b>
the <b> tag is displayed and not interpreted, as it was in previous revisions.. |
this patch should fix the problem .. a little bug still remain, if you insert some allowed HTML tags in the subject this is detected by is_html() so the Display Attribute and the Link is not applied .. the result is that the HTML is working but no elog featur is applied |
|
1277
|
Mon Jul 18 10:16:35 2005 |
| Emiliano Gabrielli | AlberT@SuperAlberT.it | Bug report | Linux | rev 1.703 | Display Subject and HTML tags, regression | rev 1.703 makes the following code not to work:
Display Subject = <b>$subject</b>
the <b> tag is displayed and not interpreted, as it was in previous revisions.. |
|
1276
|
Mon Jul 18 10:09:06 2005 |
| Emiliano Gabrielli | AlberT@SuperAlberT.it | Request | All | | Re: < img > in Display Attribute |
| Stefan Ritt wrote: | I added an escape character. If you write <b> or [b], then it gets interpreted. If you write \<b> or \[b] with the "\" in front of the tag, it does not get interpreted, thus the '\' works like an escape character. I edited your old entry with the <img> in the subject, and as you see it is now not interpreted.
The modification is in CVS and documented in the ELCode help. |
Ok, it's a good solution for me ... as using a <pre> html tag does not seem to preserve an <img> tag .. |
|
1275
|
Sat Jul 16 12:30:33 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | All | | Re: < img > in Display Attribute |
| Emiliano Gabrielli wrote: | IMHO the solution may be in allowing html code only in the cfg, not in the value of the field..
i.e., elog has to first allow html in the cfg attribute and then replace every $attribute with their values... this values as to be translated in html entities in order to solve the problem
in other wordsthe value of the attribute as to httl_encoded when displayed.. and the cfg line not
or I am loosing some point ? |
I don't like that solution. Sometimes I want to write some HTML tag myself into an attribute (like "<b>") and have this interpreted, meaning having the following word in bold, and sometimes I want to talk about HTML tags, like to tell you to use <b> for bold, and have it not interpreted. The same with the ELCode tags.
So I added an escape character. If you write <b> or [b], then it gets interpreted. If you write \<b> or \[b] with the "\" in front of the tag, it does not get interpreted, thus the '\' works like an escape character. I edited your old entry with the <img> in the subject, and as you see it is now not interpreted.
The modification is in CVS and documented in the ELCode help. |
|
1274
|
Fri Jul 15 17:28:33 2005 |
| Emiliano Gabrielli | AlberT@SuperAlberT.it | Request | All | | Re: < img > in Display Attribute | the very usefull thing my request will enable is the following:
Options Category = Info,Report,[B]Problem[I]{1}[/I][/B],Other
Preset Category = Info
Display Category = <img style="border:0; float:left; margin-right:5px" src="icons/$category.png">$category
[B]{1}[/B]ROptions Level = Notice,Warning,Alert,Fixed
{1}Preset Level = Warning
[B]{1}Display[/B] Category = <img style="border:0; float:left; margin-right:5px" src="icons/[B]$level[/B].png">[B]$category[/B]
note that this way I could use a single field to have the both the category name and the level icon .. this is specially usefull for a "problem" or "bug" category, becouse this way one can see status of the "bug"..
.. I'd really like conditional Display  |
|