attachment filename bug & Makefile issue, posted by A. Martin on Sat May 15 06:01:40 2010 
|
If I upload the file "000000_000000_file.txt", elog will chop the filename to "file.txt." Also, this effects
the file's displayed "Uploaded" time. It shows the file as being uploaded on: "Tue Nov 30 00:00:00 1999"
Note the attachment to this post.
----
Makefile has the line:
# flag for SSL support
USE_SSL = 1
However setting USE_SSL = 0 does not prevent the openssl libraries from being used. Same issue with USE_CRYPT.
You have to comment them out.
Lines 76-85 of Makefile should be replaced with this:
ifdef USE_SSL
ifneq ($(USE_SSL), 0)
CFLAGS += -DHAVE_SSL
LIBS += -lssl
endif
endif
ifdef USE_CRYPT
ifneq ($(USE_CRYPT), 0)
CFLAGS += -DHAVE_CRYPT
LIBS += -lcrypt
endif
endif
Thanks,
amartin |
attached picture size changed, posted by weiluo on Thu Jun 25 22:58:01 2009
|
Hello everyone.
Here I found a problem recently with attaching screen-shot to the elog.
I am using "elog -f xxx/xxx.gif" to make elog entry. Recently I found my attached pictures were scaled to the half of the original size horizontally appearing in the log entry, the other half of the picture was filled with black. I need to click it once to magnify the picture to see it.
Does anyone know how to solve this problem? It bugs me a lot.
By the way, I saw some pictures were produced with the name "xxx.gif.png" in the logbook directory.
Thanks, and one of the modified picture is attached.
|
|
astonished icon, posted by Elaine Cristina Franchini dos Anjos on Fri Jul 14 21:47:14 2006
|
Hi Stefan,
I've been trying to use the astonished icon, but the preview or entry
display shows only a broken image.
I found in the elogd.c at line 5556 :
{"8o", "<img src=\"%sicons/eek.png\">"}
I copied the "astonished.png" to "eek.png" and it worked.
Is it the reason of the problem ? ?)
Thanks a lot.
Regards,
Elaine |
|
any way to undelete entries?, posted by Mark Bergman on Thu Feb 21 23:23:19 2013
|
Is there any way within eLog to undelete entries? |
|
any support of encrypted logfiles?, posted by Bill Pier on Tue May 6 21:40:05 2008
|
I'm sure this topic has been visited previously, but a search of this forum didn't show any results.
Is there are support or already proven method of encrypting the logfiles that Elog serves up?
thanks,
Bill
|
|
alphabetize Quick Filter items?, posted by Dennis Seitz on Wed Aug 5 19:05:01 2009
|
Hi Stefan,
I'd like to request a feature: automatic alphabetization of the items in the Quick Filter menus.
We track quite a few detector assemblies, which are produced with non-sequential designations. It would be useful if the Quick Filter list was automatically sorted alphabetically to make it more convenient for folks to find a particular item.
I know people can always search by designation but it would be handy to have this alpha sorting feature. Would it be possible to include that in a future release?
Thanks again for a *very* useful logging system!
Dennis |
allow per-logfile attributes to be added/subtracted from the global settings, posted by Mark Bergman on Wed May 3 00:16:42 2006
|
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 |
|
admin user access admin page, not config page, posted by Szu-Ching Peckner on Tue Sep 18 17:57:47 2012
|
We have multiple logbooks. Each user is admin user for his/her own logbook.
I want user be able to modify config file, but no access to user setting, such as see user list, change password, new user, remove user.
[logbook1]
Admin user = user1
Login user = user1, user2
Allow Config = user1
List Menu commands = Admin, Config
user1 click on Admin, it opens config file, when user1 click on save, user1 is brought to Config page, which has select user list on top, Change password, Remove user, New user buttons on bottom. Is there a way that admin user has access to config file, but no access to user info at all (not even presented to them). Is there a way after user1 click save, page doesn't go to that config page?
I could put
Deny Change password =
Deny Remove user
Deny New user
so when user1 click on those buttons, user1 will get command not allowed. However I would rather have user1 not even see that page.
|
|