Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 448 of 808  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Hide attachments  Show only new entries    6457 Entries 
Goto page Previous  1, 2, 3 ... 447, 448, 449 ... 806, 807, 808   Next  
ID Date Icon Author Author Emaildown Category OS ELOG Version Subject
  1634   Fri Jan 27 13:50:10 2006 Reply mark jamesmark@majames.comQuestion 2.6.0b5Re: Quicklink does not work for one field

Stefan Ritt wrote:

mark james wrote:

mark james wrote:

Stefan Ritt wrote:

mark james wrote:
I am not so bold as to log this as a bug but one of my Quicklink fields just do not work.


Sorry my late reply, but now I have fixed this problem. The update is under SVN and will be contained in the next release.


Thanks for that. I am now using ver V2.6.1-1622. So I guess that doesn't qualify as a "next release". I wonder if there is anything I could do to work around the issue?

Mark

In fact now the dropdown seems to be working but when I 'tick' an entry, it is not being written to the ascii file.


Can you try V2.6.1-1634? I fixed several issues with ticking entries coming from "MOptions" lists.


OK. But where do I get this from? The "latest version of 19 Jan is still 1622.
  66131   Tue Dec 30 21:13:02 2008 Question Mark Langkaumark@langkau.orgQuestionLinux | Windows2.7.5Problems with SSL and Synchronization

I installed ELOG on a Linux server (CentOS 5.2) and a WinXP laptop.

- If I set both servers to non-SSL, I can synchronize with no problems.

- If I set both servers to use SSL, synchronization fails with "Error code: ssl_error_rx_record_too_long" 

- If I set one to ssl and the other non-ssl, synchronization fails with "Remote server is not an ELOG server"

Is anyone synchronizing or mirroring two ELOG servers with SSL? When either or both servers are set to use SSL, I can use either site. but I can't synchronize.

 

Thanks
  1814   Wed May 3 00:16:42 2006 Idea Mark Bergmanmark.bergman@uphs.upenn.eduRequestLinux2.6.1allow per-logfile attributes to be added/subtracted from the global settings
I think it would be a big enhancement to allow per-logbook attributes to be additions or subtractions from the global attributes, rather than replacing the global settings.

For example, the [global] section of my elogd.cfg reads:

Attributes = Author, Type, Category, Severity, Subject, Entry ID, Status
Extendable Attributes = Type, Category, Severity, Subject, Status
Options Category = Hardware, Software (OS and utilities), Software (Application), Network, Security, Other
Options Severity = None, Low, Medium, High, Critical
Options Status = Open, Closed, In-Progress, Suspended
Options Type = To-Do, Problem Report, Problem Fixed, Informational Note, Software Installation, Configuration, Other
Required Attributes = Type, Category, Subject, Status

I've also got an logbook for each server for hardware issues. Within those logbooks, I'd like to keep all the fields except the software fields, and add fields for memory and storage.

Adding 7 definitions to each server logbook makes the config file huge and difficult to edit, and it means that a future change to the global settings wouldn't propagate to the individual log files. I'd really like to do something like:

[server47]
-Options Category = Software (OS and utilities), Software (Application)
+Options Category = Storage, Memory
-Options Type = Software Installation
+Options Type = RAM Installation, Drive upgrade

As I see it, the initial "-" sign in front of an attribute or option would indicate that the fields listed should be deleted from the global set (if the field name is an exact match), and a leading "+" indicates that the given fields would be added to the global attribute of the same name, for that specific logbook.

The current behavior--without a leading "+" or "-" would be unchanged, so that existing config files don't change.

Thanks,

Mark
  1822   Sat May 6 02:12:10 2006 Idea Mark Bergmanmark.bergman@uphs.upenn.eduRequestLinux2.6.1suggestion for "new user registration" page
I'm testing elog, and one user was having difficulty creating a new account for himself. This problem had three reasons:

1. the user expected a "submit" button or some other way to exit the account registration screen to appear near the password boxes, at the bottom of the page.

2. I'm using the "Bottom text" option, which has a URL to execute a "find" (search) within elog for all open tickets. The user simply entered the info for their new account, and then clicked on the button at the bottom of the page--which would be the expected behavior.

3. In our environment, there are many logbooks (~100), as each computing device has it's own logbook. This isn't a problem on the main page, since the logbooks are grouped into 7 categories. However, the account registration page combines two functions--setting up a new account, and selecting which logbooks to subscribe to for e-mail notification. The logbooks are presented in a list (rather than groups), which causes the "Save" button at the top left to scroll off the screen before the user enters their password.


Suggestions for improving the registration page:

Put a "submit" button after the password entry.

Possibly supress the local "bottom text", or allow the specification of a different file for the registration page.

After the user has registered, then show a page allowing them to subscribe for e-mail notifcation. That page should be organized the same way as the main page, with groups. Users should be allowed to subscribe to entire groups, or to expand each group to select or unsubscribe from individual logbooks.

Thanks,

Mark
  1840   Thu May 25 19:41:51 2006 Idea Mark Bergmanmark.bergman@uphs.upenn.eduRequestLinux2.6.1add field type to automatically email CC
I've got logbooks where I'm submitting entries on behalf of other users, or where other people should be notified of the ticket. This isn't a fixed list of people, and shouldn't be hard-coded into a config file. I've got a field to enter the user's e-mail address, but there's no action associated with that data.

I'd like to see a new field type that allows the entry of e-mail addresses, where each addresses supplied with the logfile entry would be automatically "CC'ed" in the notification e-mail. Ideally, people on the CC list would be (optionally) CC'ed when there are replies or edits to the original elog entry.


For example (snippet of fictional elogd.cfg):

-------------------------------
[web site]
Welcome Title = Issues regarding the web site
MOptions Category = Add links, Change content, Broken Link, Other
CCMailTo = Notification List
Attributes = Author, Category, Severity, Subject, Entry ID, Status, User, Login
Extendable Attributes = Category, Severity, Subject, Status, User, Login, Notification List
Required Attributes = Category, Subject, Status, User
-------------------------------
  2236   Thu May 31 23:33:28 2007 Entry Mark Bergmanmark.bergman@uphs.upenn.eduQuestionLinuxV2.6.5-186how to supress checkboxes of all logbooks at registration?
Is there a way to suppress the listing of all logbooks on the New User Registration page? We've got 100 logbooks (one for each server, cluster node, or major software package). The long list makes it difficult for users to find the bottom of the registration page, and no user needs to subscribe for automatic e-mail notification for every logbook.

Thanks,

Mark
  2237   Thu May 31 23:46:31 2007 Entry Mark Bergmanmark.bergman@uphs.upenn.eduQuestionLinuxV2.6.5config settings to ensure replies to author, thread contributors, admin?
I'm having some difficulty configuring elog to ensure that the original author of an entry, any contributors to the thread, and a desginated administrator get e-mail notification for any change to the thread.

Here's a subset of the current elogd.cfg:
Attributes = Author, Type, Category, Severity, Subject, Entry ID, Status, CC E-mail To
Display Email recipients = 1
Email All = $CC E-mail To
Email All = mark.bergman@uphs.upenn.edu
Email Format = 47
Suppress default = 0
Type CC E-mail To = museremail

The "Suppress default = 0" setting is used because many people mistakenly subscribe for automatic e-mail notification of all our logbooks when they self-register. I was hoping that the "Email All" directives would override the suppression of default mail.

This configuration works partially...in that if a user specifically selects addresses in the "CC E-mail To" field, those people do get mail.

The documentation states that there can be multiple "Email All" directives, so I thought they would be additive--causing the admin address and the author to always get mail.

Is there a setting to ensure that the original author of the thread is always notified upon any change?


Thanks,

Mark
  66898   Tue Sep 14 01:15:22 2010 Warning Mark Bergmanmark.bergman@uphs.upenn.eduBug reportLinux2.8.0elog 2.8.0 as daemon crashes when editing selected threaded list

I recently upgraded elog from 2.7.8 to 2.8.0 (and moved servers, removed unused logbooks, etc.). I'm now having a problem where elog consistently crashes when attempting to edit multiple entries. This is a very common use case, as we use a "status" field, set to "open" or "closed" to track problems. When a problem is resolved, we will go to the "list" display, set it to "threaded", "select" the thread, and then edit it, to change the status field for all posts in the thread to "closed".

Now, as soon as the "edit" button is clicked, elog crashes. This happens on every thread and logbook that I've tried. The elog logfile itself doesn't show anything useful.

However, if eLog is run with "-v" in place of "-D", it does not crash.

 

Environment:

        CentOS 5.4

        eLog 2.8.0 built Aug  5 2010, 12:24:11

 

Goto page Previous  1, 2, 3 ... 447, 448, 449 ... 806, 807, 808   Next  
ELOG V3.1.5-3fb85fa6