Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 118 of 807  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    6451 Entries 
Goto page Previous  1, 2, 3 ... 117, 118, 119 ... 805, 806, 807   Next  
ID Date Icon Authordown Author Email Category OS ELOG Version Subject
  1800   Fri Apr 7 05:07:20 2006 Reply Steve Jonessteve.jones@freescale.comBug reportAll2.6.1-1668Re: elogd 2.6.1 program Crash is repeatable under Windows

Stefan Ritt wrote:

Steve Jones wrote:
BTW, Stefan, unless you can make the most recent version of a Windows eLog available I cannot test the most recent -- I do not have access to a Windows development environment. Solaris-Yes, Linux-Yes, Windoze-No.


There is a 2.6.1-4 version for Windows for download, which contains the most recent code.



Quote:
Ok, I loaded the new Windows version ELOG V2.6.1-1681. The new version has the same behavior and it is entirely related to Top Group. With a simple Top Group setup things appear to work fine until one attempts to either create or delete a new logbook. There are other quirky things - I don't think Top Group is ready for really complex setups. In fact, this URL that is constructed by elog (http://localhost:8080/Engineering%20Compute%20Change%20Logs/Test/?cmd=Config) will cause elog to coredump but only with a very complex configfile. If I simply remove the "Top" from the "Group" directive I get the expected message "Error: logbook "Engineering Compute Change Logs" not defined in elogd.cfg
Please use your browser's back button to go back".

Another interesting point of reference - I went back to 2.5.9-4 (windows) and get the same behavior.

Now, making things really simple I added Top Group support to the demo that comes with the Windows install. This configfile:
[global]
port = 8080

Show top groups = 1
Top Group Demo Groups = demo, test7

[global Demo Groups]
Theme = default
Comment = General linux tips & tricks
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Extendable Options = Category
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type

[demo]

results in this redisplay after a new logbook create I have included in an attached screenshot. Please note that everything is generally not correct. So, even though eLog does not crash with this simple config it does support my observation that as I render the congfile more complex I corrupt eLog more until it finally crashes. Stefan, I would be interested in seeing how the above config runs on one of your windows systems.
Attachment 1: elog_2.JPG
elog_2.JPG
  1802   Mon Apr 10 05:34:40 2006 Question Steve Jonessteve.jones@freescale.comRequestAll2.6.1-1684TIMEZONE modifier?
We host eLog for a number of global sites. Our logbooks use datetime attributes but the timezones are wrong attributes that are either preset (like when a logentry is created) or if we fill in an attribute from an action (like when a logentry is closed). Any possibility of adding a timezone designator to FORMAT or does one already exist?

Thanks!
  1808   Fri Apr 14 16:30:56 2006 Question Steve Jonessteve.jones@freescale.comQuestionAll2.6.1-1684Any way to move Replies from one logentry to another?
Is there anyway to reattach a reply within a logbook from one logentry to another? I guess it would be "re-associate"?
  1812   Wed Apr 19 04:48:43 2006 Agree Steve Jonessteve.jones@freescale.comQuestionAll2.6.1-1684Re: Any way to move Replies from one logentry to another?

Stefan Ritt wrote:

Steve Jones wrote:
Is there anyway to reattach a reply within a logbook from one logentry to another? I guess it would be "re-associate"?


No, this is not possible directly. You would have to make a new reply, and manually fill in the contents from the original reply. It is however possible by directly tampering the ELOG files, but that should be done only by experienced users.


Kind of what I thought but needed to ask. I think I'll leave things as they are. Thanks!
  1841   Tue May 30 17:54:21 2006 Warning Steve Jonessteve.jones@freescale.comBug reportAll2.6.1-1681Losing field 'focus' when using Conditional Attributes
Stefan, any way to address this? It appears to only be applicable when one defines conditional Options - when javascript updates the conditional lists the input focus appears to shift to the HTML edit area. I am still running ELOG V2.6.1-1681 and this is under Windows (my test system).


With version 2.6.1 rev 1681 I believe this is when I started seeing the behavior such that when a conditional attribute value is selected the focus switches to the message entry window. It looks like when the javascript cond_submit() is called for some reason on returning focus defaults to the message window. This occurs under Windows (rev 1861) and Solaris (rev 1864). I can see in function chkform() that focus is returned for checking Required attributes, but I see nothing for conditional attributes.

Thanks
  1842   Tue May 30 17:57:46 2006 Reply Steve Jonessteve.jones@freescale.comBug reportAll2.6.1-1681Re: Losing field 'focus' when using Conditional Attributes

Steve Jones wrote:
Stefan, any way to address this? It appears to only be applicable when one defines conditional Options - when javascript updates the conditional lists the input focus appears to shift to the HTML edit area. I am still running ELOG V2.6.1-1681 and this is under Windows (my test system).


With version 2.6.1 rev 1681 I believe this is when I started seeing the behavior such that when a conditional attribute value is selected the focus switches to the message entry window. It looks like when the javascript cond_submit() is called for some reason on returning focus defaults to the message window. This occurs under Windows (rev 1861) and Solaris (rev 1864). I can see in function chkform() that focus is returned for checking Required attributes, but I see nothing for conditional attributes.

Thanks



Quote:
Attributes FunctionalArea, Operation, Category

#####################################################################################################
# Start defining how the form works
##################################################
# Define FunctionalArea
#
Options FunctionalArea = NFS{1}, LDAP{2}, LoadBalancer{3}, LSF{4}, SunRay{5}, Tarantella{6}, Vital Server{7}, ClearCase{8}, CFEngine{9}, DataCenter{10}, Compute{11}, Network{12}


##################################################
# Define Operation
#
{1} Options Operation = Maintenance, SW Installation, SW Upgrade, Configuration Change, Patch Applied
{2} Options Operation = Schema Change, Maintenance, SW Installation, SW Upgrade, Configuration Change, Patch Applied
{3} Options Operation = New Service Added, Configuration Change, Maintenance, SW Installation, SW Upgrade, Patch Applied
{4} Options Operation = Schema Change, Queue Change, License Change, SW Installation, SW Upgrade, Configuration Change, Patch Applied
{5} Options Operation = Maintenance, SW Installation, SW Upgrade, Configuration Change, Firmware Upgrade, Patch Applied
{6} Options Operation = WebTop Change, Server Added, Maintenance, SW Installation, SW Upgrade, Configuration Change, Patch Applied
{7} Options Operation = New Service Added, Maintenance, SW Installation, SW Upgrade, Configuration Change, Patch Applied
{8} Options Operation = New VOB, New View, Maintenance, SW Installation, SW Upgrade, Configuration Change, Patch Applied
{9} Options Operation = SW Upgrade, Configuration Change, Patch Applied
{10} Options Operation = New HW Install, HW Maintenance, Power/UPS, HVAC, Network HW
{11} Options Operation = Maintenance, SW Installation, SW Upgrade, Configuration Change, Patch Applied
{12} Options Operation = Maintenance, SW Installation, SW Upgrade, Configuration Change, Patch Applied
Tooltip FunctionalArea = The predefined Operations areas under which a Change may be scheduled.
Tooltip Operation = Choose FUNCTIONALAREA first

##################################################
# Define Category
#
{1} Options Category = HP, Celera, Sun, Brocade, StorageTek, EMC
{2} Options Category = Supplier, Hub, Consumer,Gateway, Client
{3} Options Category = F5, CSS
{4} Options Category = Master  
{5} Options Category = SunrayServer 
{6} Options Category = TTServer, DesktopServer
{7} Options Category = WWW, NIS, LISTSRV, NTP, DNS, MTA, TWIKI, ELOG, LOGGING HOST, GSH
{8} Options Category = VOB, VIEW
{9} Options Category = ?
{10} Options Category = Cisco, Netbotz, Liebert Paging
{11} Options Category = HPUX, Solaris, Linux
{12} Options Category = Cisco
Tooltip Category = Optional attribute. Please use for furthur classification.
  1864   Fri Jun 23 19:24:12 2006 Agree Steve Jonessteve.jones@freescale.comBug reportAll2.6.1-1681Re: Losing field 'focus' when using Conditional Attributes

Stefan Ritt wrote:

Steve Jones wrote:
It appears to only be applicable when one defines conditional Options - when javascript updates the conditional lists the input focus appears to shift to the HTML edit area. I am still running ELOG V2.6.1-1681 and this is under Windows (my test system).


It was some new code used for inline images. If you upload an inline image, an extra window opens which lets you select the image file. After that operation, you want to have the focus back at the text box. Unfortunately this also happened now after the JavaScript update of conditional attributes. I fixed that in the new version 2.6.1-6.



Quote:
Just compiled and tested on Solaris 8 -- works great!!
  1866   Tue Jul 4 07:04:19 2006 Reply Steve Jonessteve.jones@freescale.comQuestionMac OSX2.6.1Re: Canīt run command "make" in OSX

Mats McLund wrote:
Hello.

I think to test Elog in Mac G5 with OSX 10.4.6.

In the manual is following installationtext:

"Installation from the tarball:
Download the latest elog-x.x.x.tar.gz package.
Expand the compressed TAR file with tar -xzvf elog-x.x.x.tar.gz. This creates a subdirectory elog-x.x.x where x.x.x is the version number. In that directory execute make, which creates the executables elogd, elog and elconv."

The problem is when i try to run the command "make" in ~/elog-2.6.1 subdirectory. I get following message:
-bash: make: command not found

Now, Im not an "UNIX-hacker" so I will be glad if anyone maybe can help me?



Best regardīs
Mats McLund



Quote:
Typically one would install the Gnu compiler series and with that come 'gmake'. Barring that, and not knowing anything about OSx, if OSx comes with its own compiler series then make might be somewhere on the system but not in your path. Go to http://gcc.gnu.org/ and see if you an find a pre-built version of gcc -- all I found mentioned "darwin". Perhaps Apple has something in the way of a development colleciton?
Goto page Previous  1, 2, 3 ... 117, 118, 119 ... 805, 806, 807   Next  
ELOG V3.1.5-3fb85fa6