| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1639
|
Sat Jan 28 12:54:03 2006 |
 | Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.6.1 CVS | Re: Running elog as ordinnary user |
| G. Vandemoortele wrote: | Started via root (# /usr/sbin/elogd -c /home/gv/.elog/elogd.cfg -x), it works,
but via "gv" ($ /usr/sbin/elogd -c /home/gv/.elog/elogd.cfg -x), it doesn't. |
I tried with your config file, and it works fine (see attached screendump). So I have no clue right now why it is not working in your case. |
| Attachment 1: screendump.png
|
|
|
1642
|
Mon Jan 30 12:27:08 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.6.1 | Re: Running ELOG under Apache |
| Dimitrios Tsirigkas wrote: | | Sorry if this has been asked elsewhere and I'm missing it. I want to stop users from accessing my elog by loading the URL: http://mycomputerURL:8080 and only make it accessible through http://mycomputerURL/elog. The end goal would be to use Apache to control access. I followed the instructions under "Running elogd under Apache" in the admin guide, but what that did was simply to redirect browsers trying to load ttp://mycomputerURL/elog to http://mycomputerURL:8080. |
If you want to have user-level access control, you need to do that with the config option
Password file = ...
Then, if you have the
URL = http://mycomputerURL/elog
statement in your config file, you get redirected from elogd after each login automatically to that URL. If you physically want to block the 8080 port, you have to do that on the operating system level, like with iptables or ipchains. |
|
1650
|
Mon Feb 6 08:27:40 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Other | 2.6.1 | Re: compiling elog 2.6.1 on solaris platform |
| Angus Au wrote: | | ld: fatal: library -lutil: not found |
The util library was added recently because of the new shell substitution functionaly, which requires the forkpty() function call. If you know in which library the forkpty is available on solaris, the makefile could be adjusted accordingly. If the forkpty is not available at all, we have to disable the shell substitution under solaris via conditional compilation. |
|
1651
|
Mon Feb 6 12:52:09 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Other | 2.6.1 | Re: [261] problem with month selection |
> I have several date-fields defined in my logboek. But when I click the icon and select another month the pop-up
> window get's filled with the contants of the logboek instead of the date-selection.
Ups, that problem must have been there for quite some time now. I fixed it in the current SVN version. |
|
1652
|
Mon Feb 6 12:54:25 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.6.1 | Re: elog allows me to create user "blahblah " |
| Dimitrios Tsirigkas wrote: | | By the way, it is also possible to create a user that doesn't have a password! Shouldn't that be forbidden? |
Well, some people want that! |
|
1653
|
Mon Feb 6 12:58:26 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.6.1 | Re: elog allows me to create user "blahblah " |
| Dimitrios Tsirigkas wrote: | | I noticed that when I register a username that contains whitespaces (eg "boing "), elog allows me to create the user of that name and updates the password file accordingly. It doesn't log me in, but it gives me no error message either. I also found that if I repeat the process it adds yet another entry in the password file, by the same name "boing ". Is that a bug or is there something wrong with my configuration? |
Well, I tell you what is wrong: The form says explicitly (name may not contain blanks) and you did not listen 
I can add a simple check if the name contains blanks, but then some people will come up with other strange characters (@#$%), and I'm not sure which of those gives problems. If you test this carefully and tell me which characters to make forbidden, I will happyly add a simple check. |
|
1656
|
Mon Feb 6 16:48:17 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Other | 2.6.1 | Re: compiling elog 2.6.1 on solaris platform |
| Steve Jones wrote: | | I have checked and can find no reference within Sun documents regarding the support of the forkpty() function. I have not been following elog development lately -- what is shell substitution supposed to buy us? |
See the config manual and look for $shell |
|
1657
|
Mon Feb 6 16:53:41 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Linux | 2.6.1 | Re: elog allows me to create user "blahblah " |
| Dimitrios Tsirigkas wrote: | | I wouldn't want some imposter to start entering stuff under the username of another user, so it would be nice if I could have some way of forcing them to have a password, even if it's a one-letter password. |
Ok, I added an empty password check. If too many people will complain, I will make it a flag. |