Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 174 of 808  Not logged in ELOG logo
 Find |  Login |  Help 
New entries since:Thu Jan 1 01:00:00 1970
 Full | Summary | Threaded | Hide attachments  Show all entries    6457 Entries 
Goto page Previous  1, 2, 3 ... 173, 174, 175 ... 806, 807, 808   Next  
ID Date Icon Author Author Email Category OS ELOG Version Subjectdown
  1342   Tue Jul 26 22:05:24 2005 Reply Juliana Pengjpeng@yorku.caRequestLinuxV2.6.0Re: hide attributes when view the logbook

Stefan Ritt wrote:


Use "list display = <attribute list>" to specify which attributes to show in the listing page. RTFM.


Thanks. "List display" is what we need.

But is there a way to control to hide or view the attributes? so that we don't need to change the elog.conf file each time.

For example, add a menu "expend" in "Find menu commands", we can click to view all the attributes or just view the attributes defined in "List Display"

Or use "{1} List Display = ....", we can view all the attributes at list page, but if selecting SunOS, only show attributes in List Display
  1344   Wed Jul 27 09:07:17 2005 Reply Stefan Rittstefan.ritt@psi.chRequestLinuxV2.6.0Re: hide attributes when view the logbook

Juliana Peng wrote:
But is there a way to control to hide or view the attributes? so that we don't need to change the elog.conf file each time.

For example, add a menu "expend" in "Find menu commands", we can click to view all the attributes or just view the attributes defined in "List Display"

Or use "{1} List Display = ....", we can view all the attributes at list page, but if selecting SunOS, only show attributes in List Display


In that case I would suggest two separate logbooks, for for SunOS and one for others. This way you can manage two separate sets of attributes.
  1346   Wed Jul 27 15:49:16 2005 Reply Juliana Pengjpeng@yorku.caRequestLinuxV2.6.0Re: hide attributes when view the logbook

Stefan Ritt wrote:

In that case I would suggest two separate logbooks, for for SunOS and one for others. This way you can manage two separate sets of attributes.


We don't want separate logbooks, sorry for the misleading. I was trying to put two request together.

1. We have several user using the logbook. Is there a way each one has his own "List Display". In our case the user also is an attribute(SysAdmin) in logbook:

Attributes = Name, SysAdmin, Manufacturer, Model, Serial Number, Description, ENV, 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 SysAdmin = user1{1}, user2{2}, user3{3}

so one way we can think of is using "{1} List Display = ...."
"{2} List Display = ...."
"{3} List Display = ...."
because most of the time the user is interested in his own machine. Maybe you have better suggestion.

2. We need to change elog.conf file to use or not use "List Display". Is there a way to control it through web? If this is not applicable. It's fine, we won't change the view frequently.
  1347   Wed Jul 27 15:56:53 2005 Reply Stefan Rittstefan.ritt@psi.chRequestLinuxV2.6.0Re: hide attributes when view the logbook

Juliana Peng wrote:
We don't want separate logbooks, sorry for the misleading. I was trying to put two request together.


I understood you correctly. What I was trying to say is that what you currently request possible with the current version and will not be implemented soon. But you can partly obtain what you want by having two logbooks. Make one logbook which has fewer attributes, and which will receive all SunOS entries. Make another one with all the attributes. Although this will become separate logooks, you can "think" of them as one logbook with two different sections. There is even the trick of forcing the data directory to be the same (via the "data dir") option, so both logbooks will "look" at the same database. Make one logbook the "master" having all the attributes. That's where you enter your information. Them make one or more logbooks looking at the same data, but make them read-only. Each logbook can have a separate set of attributes, access rights etc, but all of them show the same data.

I know this is not the perfect solution, but at least something which can be done already now.
  1348   Wed Jul 27 16:31:33 2005 Smile Juliana Pengjpeng@yorku.caRequestLinuxV2.6.0Re: hide attributes when view the logbook

Stefan Ritt wrote:

I understood you correctly. What I was trying to say is that what you currently request possible with the current version and will not be implemented soon. But you can partly obtain what you want by having two logbooks. Make one logbook which has fewer attributes, and which will receive all SunOS entries. Make another one with all the attributes. Although this will become separate logooks, you can "think" of them as one logbook with two different sections. There is even the trick of forcing the data directory to be the same (via the "data dir") option, so both logbooks will "look" at the same database. Make one logbook the "master" having all the attributes. That's where you enter your information. Them make one or more logbooks looking at the same data, but make them read-only. Each logbook can have a separate set of attributes, access rights etc, but all of them show the same data.

I know this is not the perfect solution, but at least something which can be done already now.


Thank you so much. We'll try it. Waiting for your next version.
  66372   Thu Jun 4 14:44:11 2009 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.7.5-2130Re: help with substituting subjects

 

Alexander Withers wrote:

I am trying to add additional information to the subject of new entries:

Subst subject = $subject [INCIDENT $message id]
Subst on reply subject = Re: $subject
Fixed Attributes Reply = Subject

However, the new entry subject looks like:

this is my subject [INCIDENT this is my subject [INCIDENT $message id]

I'm not sure if there's a problem with the substitution or if this is just not allowed (I'm having LISP flashbacks).

By the way, if I use "Subst on reply subject" I get the behavior I would like but the original entry in the thread doesn't contain the appended data:

Subst on reply subject = Re: $subject [INCIDENT $message id]

Any help would be appreciated.

Alex

 

The problem here is that the subsitution is executed before the entry is committed to the database. The message ID is assigned however only in the commit. So at the time of the substitution, the $message id is not available. When you do the reply however, the message id is valid and subsituted correctly. I see at this moment no clever solution for your problem (maybe "Subst on edit", but then you have to edit/submit each message manually once).

  630   Wed Jul 28 21:54:36 2004 Reply Stefan Rittstefan.ritt@psi.chBug reportAll2.5.4?Re: getcfg problem in v1.410: Truncation of long config strings
> Just compiled 1.410 and have run into an issue that *may* have been
> introduced in 1.393.
> 
> Config file directives such as "Welcome title" could be very long strings. 
> After compiling 1.410, our "Welcome title" is truncated and, while I haven't
> counted the actual chars, I suspect that the truncation happens at 1024
> characters.  The procedure 'getcfg' has a declared passed paramater "int
> vsize". 

Actually before 1.393 you got a buffer overflow if any string in the
configuration file was longer than 500 chars, so it's a miracle that your elogd
did not crash on the long Welcome Title. I added the "vsize" parameter to avoid
such crashes. To satisfy your need for a long Welcome title, I increased the
string size for that particular case to 10000 chars. Hope this is enough.
  631   Wed Jul 28 22:07:31 2004 Agree Steve Jonessteve.jones@freescale.comBug reportAll2.5.4?Re: getcfg problem in v1.410: Truncation of long config strings
> > Just compiled 1.410 and have run into an issue that *may* have been
> > introduced in 1.393.
> > 
> > Config file directives such as "Welcome title" could be very long strings. 
> > After compiling 1.410, our "Welcome title" is truncated and, while I haven't
> > counted the actual chars, I suspect that the truncation happens at 1024
> > characters.  The procedure 'getcfg' has a declared passed paramater "int
> > vsize". 
> 
> Actually before 1.393 you got a buffer overflow if any string in the
> configuration file was longer than 500 chars, so it's a miracle that your elogd
> did not crash on the long Welcome Title. I added the "vsize" parameter to avoid
> such crashes. To satisfy your need for a long Welcome title, I increased the
> string size for that particular case to 10000 chars. Hope this is enough.

Hmmm, it is a wonder.  Our welcome text was not significantly longer (about 20
chars longer) so perhaps . . . ?

Thanks, will recompile and report back.
Goto page Previous  1, 2, 3 ... 173, 174, 175 ... 806, 807, 808   Next  
ELOG V3.1.5-3fb85fa6