| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
66042
|
Wed Nov 12 16:41:44 2008 |
 | Carl Shirey | carl.shirey@pw.utc.com | Question | Linux | 2.7.2-3 | Error: Failed dependencies: |
I went to upgrade to the new version of elog I receive a error message that is.
error: Failed dependencies:
libssl.so.6 is needed by elog-2.7.5-1.i386
rtld(GNU_HASH) is needed by elog-2.7.5-1.i386
Do I need these dependencies for elog to work? If I do need them where do I get them for Suse 10.2.
Thank you for any help.
Carl
|
|
66059
|
Mon Nov 17 19:56:04 2008 |
 | Carl Shirey | carl.shirey@pw.utc.com | Question | Linux | 2.7.2-3 | Re: Error: Failed dependencies: |
| Stefan Ritt wrote: |
|
| Carl Shirey wrote: |
|
I went to upgrade to the new version of elog I receive a error message that is.
error: Failed dependencies:
libssl.so.6 is needed by elog-2.7.5-1.i386
rtld(GNU_HASH) is needed by elog-2.7.5-1.i386
Do I need these dependencies for elog to work? If I do need them where do I get them for Suse 10.2.
Thank you for any help.
Carl
|
Starting from 2.7.5, elog needs libssl for any https:// connection. Just install the RPM like you install any other RPM. Now I'm not familar with SUSE, but I found links like that:
http://lenz.homelinux.org/RPMs/
from where you can obtain RPMs. You might have to adjust your YaST installation sources. The package you need should be named opensll-xxx where xxx is some number.
|
Thank you
I will look into it.
Carl |
|
67141
|
Tue Nov 1 14:04:50 2011 |
| Carl Shirey | carl.shirey@pwr.utc.com | Question | Linux | 2.7.2-3 | Search Option |
Is there a way to setup a search, to search several log books but not all the logs books at one time?
Thanks
Carl |
|
66725
|
Sun Feb 28 07:25:10 2010 |
| Capt. Ben Smith | ben@maperl.com | Question | All | 2280 | Re: Single Button Entry |
| Geoff Ellis wrote: |
|
For our application we have a lot of very common events we would like to log. It would be preferable that for certain events/entries we could setup a single button / quick entry method. Is there away to accomplish this?
|
This would be of value for me as well. I'm trying to develop a event log for a research ship. Thanks. -ben |
|
265
|
Fri Apr 4 00:50:31 2003 |
| Byron | | Question | | | Login user problem |
When I use the <Login user => option to specify what users I want to be
able to login into the different logbooks it does not seem to work. Is
there something else you are supposed to do to restrict what logbooks users
can log into? |
|
266
|
Fri Apr 4 00:53:00 2003 |
| Byron | | Bug report | | | Password Problem |
I noticed that when I put in a password such as <test1> a person can login
with the password <test2> or any other number at the end. Is the
encryption not able to tell the difference between numbers? The encrypted
passwords even look the same in the password file. Is this a bug? |
|
269
|
Fri Apr 4 19:46:56 2003 |
| Byron | cryogaze@easystreet.com | Question | | | Re: Login user problem |
> > When I use the <Login user => option to specify what users I want to be
> > able to login into the different logbooks it does not seem to work. Is
> > there something else you are supposed to do to restrict what logbooks
users
> > can log into?
>
> First, you need version 2.3.4 or later, second, you need a "password file =
> xxx" entry in your elogd.cfg to turn on user-level password access. If both
> is true and you still don't succeed, send me your elogd.cfg.
>
> - Stefan
Ok, I installed the latest version and this is fixed. Thanx! |
|
270
|
Fri Apr 4 19:49:32 2003 |
| Byron | cryogaze@easystreet.com | Bug report | | | Re: Password Problem |
> > I noticed that when I put in a password such as <test1> a person can
login
> > with the password <test2> or any other number at the end. Is the
> > encryption not able to tell the difference between numbers? The
encrypted
> > passwords even look the same in the password file. Is this a bug?
>
> This is really strange. Encryption only works on ASCII characters and does
> not distinguish between letters and digits. When I try to reporoduce that,
> the system distinguishes well between "test1" and "test2". The first gives
> encrypted "dGVzdDE=" and the second gives "dGVzdDI=", note the
different "E"
> and "I". So I have no clue right now what is wrong in your installation. If
> running under Linux, you can compile elogd after adding "-DHAVE_CRYPT"
and "-
> lcrypt" to the Makefile to use the standard Linux crypt() function, but I
> would rather like to understand what is wrong in your case.
>
> - Stefan
Ok, try it with the passwords <hello1> and <hello2>. Then when you go to log
in, put in the password of <hello> with any single number after it and let me
know if the problem shows up for you because that is the password I was
using. When I look at it encrypted in the passwd file they look the same. I
also installed the latest version today which is newer than the one I was
using before and it still does it. I appreciate your time.
Byron |