Enable user to view only, not post/delete., posted by Denis Perevalov on Tue Jul 20 21:03:10 2010
|
Hi,
I have just discovered elog and I absolutely love it.
I have a question. Is there a way to enable user to view only, not post/delete in my elog. Also I would like to allow them to view only certain categories of my messages.
Regards,
Denis |
Re: Enable user to view only, not post/delete., posted by Stefan Ritt on Wed Jul 21 12:33:39 2010
|
| Denis Perevalov wrote: |
|
I have a question. Is there a way to enable user to view only, not post/delete in my elog. Also I would like to allow them to view only certain categories of my messages.
|
The first thing you can do with "Guest menu commands", where you enable only those commands which can't change or delete entries. The second thing you can only do if you put your entries into two separate logbooks, a public and a private one. |
|
elogd -C failing to sync password file with "Received invalid response from elogd server" message, posted by John Rouillard on Sun May 2 17:43:06 2010
|
Hello:
I am running release 2.7.8 of elog. I am using the cloning/syncing features
to maintain a backup/slave and at some point it stopped cloning the password
file.
Operating systems/software:
master: ubuntu 10.4 using locally compiled elog 2.7.8-2278
slave: solaris 10 using locally compile elog 2.7.8 without SSL support
A sample run (hostname edited - available by private email if needed) is:
$../elogd -C http://host.example.org:8080/
Overwrite local "elogd.cfg"? [y]/n: y
Remote configuration successfully received.
Option "Mirror server = http://host.example.org:8080/" added to config file.
Option "URL = xxx" has been outcommented from config file.
Retrieve remote password files? [y]/n: y
Received invalid response from elogd server at http://host.example.org:8080/Discussion/
Running with -v doesn't produce any useful diagnostics as to what the invalid response is.
Trussing the process (again with host name editing) shows:
send(3, 0xFFBEE890, 93, 0) = 93
G E T / D i s c u s s i o n / ? c m d = G e t P w d F i l e
H T T P / 1 . 0\r\n C o n n e c t i o n : C l o s e\r\n H o s
t : h o s t . e x a m p l e . o r g : 8 0 8 0\r\n\r\n
poll(0xFFBEC070, 1, 30000) = 1
recv(3, 0x011057B0, 251000, 0) = 119
H T T P / 1 . 1 4 0 4 N o t F o u n d\r\n S e r v e r :
E L O G H T T P 2 . 7 . 8 - 2 2 7 8\r\n C o n t e n t - T y
p e : t e x t / h t m l ; c h a r s e t = I S O - 8 8 5 9 - 1
\r\n C o n n e c t i o n : C l o s e\r\n\r\n
If logged in as myself I go to http://host.example.org:8080/Discussion/?cmd=GetPwdFile
I do get the data so this looks like a password/authentication issue.
I have added Mirror user = rouilj to elogd.cfg, and it is present in the cloned elogd.cfg
but still no joy. I also copied the passwd file to the clone and made sure that it was being
successfully found and opened during the clone operation.
So where do I go from here in trying to troubleshoot the problem?
-- rouilj |
|
Re: elogd -C failing to sync password file with "Received invalid response from elogd server" message, posted by John Rouillard on Sun May 9 18:12:28 2010
|
Does anybody have any ideas? Should I post a config or something?
-- rouilj |
|
Re: elogd -C failing to sync password file with "Received invalid response from elogd server" message, posted by Stefan Ritt on Mon May 10 09:55:12 2010
|
Hi Rouilj,
re-posting your bug report doe not help. If I'm not replying immediately it means I'm pretty busy with other things, so just be patient.
Your problem is related to the reply from the server you posted. After you send
GET /Discussion/?cmd=GetPwdFile
you should get the login page, which starts with
HTTP/1.1 200 Document follows
....
<title>ELOG Login</title>
....
but you do get
HTTP/1.1 404 Not Found
....
The best thing to diagnose this problem is to run the server with the "-v" flag, so you don't have to run truss. Then compare the request sent by your cloning process (your GET /Discussion/?cmd=GetPwdFiel from above) and compare it if you send from your browser
http://host.example.org:8080/Discussion/?cmd=GetPwdFile
now without sending any cookies. Maybe you can figure out why the server replies with a 404 instead of a 200 when run from the cloning process. Try a very simple elogd.cfg on your sever side, just the basic thing with a "Password file = ..." setting. Do you have any blanks in your logbook name? Are you using Apache as a proxy?
Anyhow, if this does not work for you, just copy your password file manually as you did already. The rest should then work fine for you.
- Stefan |
|
Re: elogd -C failing to sync password file with "Received invalid response from elogd server" message, posted by John Rouillard on Mon May 17 04:01:16 2010
|
| Stefan Ritt wrote: | Hi Rouilj,
re-posting your bug report doe not help. If I'm not replying immediately it means I'm pretty busy with other things, so just be patient.
|
Fair enough. I just saw posts after mine being responded to and I wasn't sure if my choice of icon
was causing it to be filtered out or not.
| Stefan Ritt wrote: |
Your problem is related to the reply from the server you posted. After you send
GET /Discussion/?cmd=GetPwdFile
you should get the login page, which starts with
HTTP/1.1 200 Document follows
....
<title>ELOG Login</title>
....
but you do get
HTTP/1.1 404 Not Found
....
The best thing to diagnose this problem is to run the server with the "-v" flag, so you don't have to run truss. Then compare the request sent by your cloning process (your GET /Discussion/?cmd=GetPwdFiel from above) and compare it if you send from your browser
http://host.example.org:8080/Discussion/?cmd=GetPwdFile
|
Using the url above from mozilla without being logged into the elogd server, elogd -v shows:
GET /Discussion/?cmd=GetPwdFile HTTP/1.1
Host: rouilj.dyndns.org:8080
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3 (.NET CLR 3.5.30729)
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Cookie: elmode=Summary; urem=1
==== Return ================================
HTTP/1.1 404 Not Found
Server: ELOG HTTP 2.7.8-2278
Content-Type: text/html;charset=ISO-8859-1
Content-Length: 665
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
<META NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW">
<title>ELOG error</title>
<link rel="stylesheet" type="text/css" href="default.css">
</head>
<body><center>
<table class="dlgframe" width="50%" cellpadding="1" cellspacing="0"<tr><td class="errormsg">Error: Command "<b>GetPwdFile</b>" not allowed</td></tr>
<tr><td class="errormsg"><script language="javascript" type="text/javascript">
document.write("<button type=button onClick=history.back()>Back</button>");
</script>
<noscript>
Please use your browser's back button to go back
</noscript>
</td></tr>
</table>
</center></body></html>
It looks like it's not redirecting to the login page and returning a 404 instead.
If I log in and submit the same URL, it displays the password file as expected.
I think I kind of see what's happening here. In is_command_allowed you add the GetPwdFile to the list of
allowed command but only if is_admin_user is true. Since the user is guest at that point, I assume
is_admin_user returns false making is_command_allowed return false. Then the redirect is attempted by this
code sequence:
if (!is_command_allowed(lbs, command)) {
/* redirect to login page for new command */
if (strieq(command, loc("New")) && !isparam("unm")) {
check_user_password(lbs, "", "", _cmdline);
return;
}
but to me that looks like it will execute only if the command contains the word new
(or it's translated equivalent if I understand loc() properly)?? Since the command string
GetPwdFile doesn't match no login screen is presented by check_user_password.
| Stefan Ritt wrote: |
now without sending any cookies. Maybe you can figure out why the server replies with a 404 instead of a 200 when run from the cloning process. Try a very simple elogd.cfg on your sever side, just the basic thing with a "Password file = ..." setting. Do you have any blanks in your logbook name? Are you using Apache as a proxy?
Anyhow, if this does not work for you, just copy your password file manually as you did already. The rest should then work fine for you.
- Stefan |
No apache in the mix (although I may be adding it in the future), no blanks in the
logbook names.
-- rouilj |
Re: elogd -C failing to sync password file with "Received invalid response from elogd server" message, posted by John Rouillard on Mon May 17 04:19:29 2010 
|
| John Rouillard wrote: |
I think I kind of see what's happening here. In is_command_allowed you add the GetPwdFile to the list of
allowed command but only if is_admin_user is true. Since the user is guest at that point, I assume
is_admin_user returns false making is_command_allowed return false. Then the redirect is attempted by this
code sequence:
if (!is_command_allowed(lbs, command)) {
/* redirect to login page for new command */
if (strieq(command, loc("New")) && !isparam("unm")) {
check_user_password(lbs, "", "", _cmdline);
return;
}
but to me that looks like it will execute only if the command contains the word new
(or it's translated equivalent if I understand loc() properly)?? Since the command string
GetPwdFile doesn't match no login screen is presented by check_user_password.
|
The attached patch (also included inline) seems to fix the problem. I am sure it can be done more cleanly but...
--- elogd.c~ 2009-12-02 05:53:44.000000000 -0500
+++ elogd.c 2010-05-16 21:58:14.000000000 -0400
@@ -26236,6 +26236,10 @@
check_user_password(lbs, "", "", _cmdline);
return;
}
+ if (strieq(command, loc("GetPwdFile")) && !isparam("unm")) {
+ check_user_password(lbs, "", "", _cmdline);
+ return;
+ }
strencode2(str2, command, sizeof(str3));
sprintf(str, loc("Error: Command \"<b>%s</b>\" not allowed"), str2);
-- rouilj |
|
Re: elogd -C failing to sync password file with "Received invalid response from elogd server" message, posted by Stefan Ritt on Tue May 18 13:21:32 2010
|
| John Rouillard wrote: |
| John Rouillard wrote: |
I think I kind of see what's happening here. In is_command_allowed you add the GetPwdFile to the list of
allowed command but only if is_admin_user is true. Since the user is guest at that point, I assume
is_admin_user returns false making is_command_allowed return false. Then the redirect is attempted by this
code sequence:
if (!is_command_allowed(lbs, command)) {
/* redirect to login page for new command */
if (strieq(command, loc("New")) && !isparam("unm")) {
check_user_password(lbs, "", "", _cmdline);
return;
}
but to me that looks like it will execute only if the command contains the word new
(or it's translated equivalent if I understand loc() properly)?? Since the command string
GetPwdFile doesn't match no login screen is presented by check_user_password.
|
The attached patch (also included inline) seems to fix the problem. I am sure it can be done more cleanly but...
--- elogd.c~ 2009-12-02 05:53:44.000000000 -0500
+++ elogd.c 2010-05-16 21:58:14.000000000 -0400
@@ -26236,6 +26236,10 @@
check_user_password(lbs, "", "", _cmdline);
return;
}
+ if (strieq(command, loc("GetPwdFile")) && !isparam("unm")) {
+ check_user_password(lbs, "", "", _cmdline);
+ return;
+ }
strencode2(str2, command, sizeof(str3));
sprintf(str, loc("Error: Command \"<b>%s</b>\" not allowed"), str2);
-- rouilj |
Ok, now I got it! The problem was that you used "Guest menu commands = ..." and I did not. So the behavior is different with that option, which is why I could not reproduce your problem initially. Now I could reproduce it and the cleanest fix is this:
--- elogd.c (revision 2294)
+++ elogd.c (working copy)
@@ -15704,7 +15704,7 @@
fgets(pwd, sizeof(pwd), stdin);
while (pwd[strlen(pwd) - 1] == '\n' || pwd[strlen(pwd) - 1] == '\r')
pwd[strlen(pwd) - 1] = 0;
- } else if (status != 200 && status != 302) {
+ } else if (status != 200 && status != 302 && status != 404) {
xfree(buffer);
*strchr(str, '?') = 0;
which is just accept the 404 response and not abort the cloning process. |
|
Re: elogd -C failing to sync password file with "Received invalid response from elogd server" message, posted by John Rouillard on Tue May 18 21:17:35 2010
|
| Stefan Ritt wrote: |
Ok, now I got it! The problem was that you used "Guest menu commands = ..." and I did not. So the behavior is different with that option, which is why I could not reproduce your problem initially. Now I could reproduce it and the cleanest fix is this:
--- elogd.c (revision 2294)
+++ elogd.c (working copy)
@@ -15704,7 +15704,7 @@
fgets(pwd, sizeof(pwd), stdin);
while (pwd[strlen(pwd) - 1] == '\n' || pwd[strlen(pwd) - 1] == '\r')
pwd[strlen(pwd) - 1] = 0;
- } else if (status != 200 && status != 302) {
+ } else if (status != 200 && status != 302 && status != 404) {
xfree(buffer);
*strchr(str, '?') = 0;
which is just accept the 404 response and not abort the cloning process. |
Yup. My settings are:
Guest menu commands = List, Last 10, Find, Login, Help
Guest List Menu commands = List, Last 10, Find, Login, Help
Ok, so this patch fixes the problem on the client side (rather than the server side like my patch) of the
cloning process. I can't tell from the patch above but will this fix allow the cloning process to "complete"
but without the password file being copied, or does code outside the patched section try to login and get
the password file?
-- rouilj |
|
Re: elogd -C failing to sync password file with "Received invalid response from elogd server" message, posted by Stefan Ritt on Wed May 19 09:57:50 2010
|
| John Rouillard wrote: | Ok, so this patch fixes the problem on the client side (rather than the server side like my patch) of the
cloning process. I can't tell from the patch above but will this fix allow the cloning process to "complete"
but without the password file being copied, or does code outside the patched section try to login and get
the password file? |
Well, why don't you give it a try and let me know if the is any problem left? |
|
Re: elogd -C failing to sync password file with "Received invalid response from elogd server" message, posted by John Rouillard on Thu May 20 03:37:59 2010
|
| Stefan Ritt wrote: |
| John Rouillard wrote: | Ok, so this patch fixes the problem on the client side (rather than the server side like my patch) of the
cloning process. I can't tell from the patch above but will this fix allow the cloning process to "complete"
but without the password file being copied, or does code outside the patched section try to login and get
the password file? |
Well, why don't you give it a try and let me know if the is any problem left? |
Sorry to report that it fails same as originally with:
Received invalid response from elogd server at http://example.org:8080/Discussion/
However there was a fuzz of 12 lines when I applied the patch, but I think it got the right line.
-- rouilj |
|
Re: elogd -C failing to sync password file with "Received invalid response from elogd server" message, posted by John Rouillard on Sat Jun 12 05:55:39 2010
|
I pulled svn revision 2299 from svn and built it on both server and client side. It is working
properly now.
Thanks for the patch.
-- rouilj |
|
change design part of the discussion board, posted by Heinzmann on Sun Jun 6 22:54:55 2010
|
Hello Stefan,
If I would like to change the design of the attached part of the discussion board like:
deleting OS: (including blue box) Linux Windows Mac OSX All Other (including green box)
Where and how could I do this?
Thank you
|
|
Re: change design part of the discussion board, posted by Stefan Ritt on Tue Jun 8 09:02:03 2010
|
| Heinzmann wrote: |
|
Hello Stefan,
If I would like to change the design of the attached part of the discussion board like:
deleting OS: (including blue box) Linux Windows Mac OSX All Other (including green box)
Where and how could I do this?
Thank you
|
Well, the official forum at midas.psi.ch cannot be changed by you. But if you installed a local logbook similar to the one here, you simple go and edit the configuration file elogd.cfg. Please read the documentation for further information. |
|
Re: change design part of the discussion board, posted by Heinzmann on Tue Jun 8 23:08:41 2010
|
| Stefan Ritt wrote: |
|
| Heinzmann wrote: |
|
Hello Stefan,
If I would like to change the design of the attached part of the discussion board like:
deleting OS: (including blue box) Linux Windows Mac OSX All Other (including green box)
Where and how could I do this?
Thank you
|
Well, the official forum at midas.psi.ch cannot be changed by you. But if you installed a local logbook similar to the one here, you simple go and edit the confitguration file elogd.cfg. Please read the documentation for further information.
|
Stefan,
I have done the changes to my logbock, but I think I have done something wrong. As an example, the window where you write in your note is not sized anymore like before. I have to scroll a lot to the right to see the right border of the window.
The only thing I have done was try to delete: the OS: Linux Window Mac OSC All Other info.
Please could you help me out?
|
|
Re: change design part of the discussion board, posted by Stefan Ritt on Wed Jun 9 08:26:20 2010
|
| Heinzmann wrote: |
|
I have done the changes to my logbock, but I think I have done something wrong. As an example, the window where you write in your note is not sized anymore like before. I have to scroll a lot to the right to see the right border of the window.
The only thing I have done was try to delete: the OS: Linux Window Mac OSC All Other info.
|
How should I know what you have done wrong if you don't tell me. It's like if you call your PC manufacturer and tell him: "My PC is not working, what is wrong?". So please send me your elogd.cfg, and make a few screen shots so that I know what is going on. |
|
inline-code, posted by Yoshio Imai on Tue Jun 8 15:48:06 2010
|
Hi, Stefan!
Sometimes, it is annoying that the [code] -Tag creates a line break, because there are situations where verbatim text inside the regular text flow is desirable (just like here). I would like to request an additional elcode-tag [ilcode] (in-line code) which translates to <code> instead of <pre> .
Cheers
Yoshio |
|
Re: inline-code, posted by Stefan Ritt on Tue Jun 8 16:33:07 2010
|
| Yoshio Imai wrote: | Sometimes, it is annoying that the [code] -Tag creates a line break, because there are situations where verbatim text inside the regular text flow is desirable (just like here). I would like to request an additional elcode-tag [ilcode] (in-line code) which translates to <code> instead of <pre> .
Yoshio |
The [code] tags produce <pre>...</pre> tags for multi-line listings, where several spaces should not be dropped to keep the formatting of some source code for example. I also want it sometimes in a single line, so what I do is to use a [FONT=Courier New] tag, which produces output very similar to <code>, but without line breaks. |
Restricting logbook view, posted by Allen on Fri May 21 14:37:26 2010
|
Is there anyway to restrict access so that a user can only see the log entries they post or only replies to their log entry? I know it is possible to restrict editing to only posts they submitted, but I have a need to not even allow them to see other posts except for what they submitted and I am wondering if this is possible currently, or if this is planned, or could be planned for a future version?
Thanks,
Allen |
|
Re: Restricting logbook view, posted by Stefan Ritt on Tue Jun 8 12:02:36 2010
|
| Allen wrote: |
|
Is there anyway to restrict access so that a user can only see the log entries they post or only replies to their log entry? I know it is possible to restrict editing to only posts they submitted, but I have a need to not even allow them to see other posts except for what they submitted and I am wondering if this is possible currently, or if this is planned, or could be planned for a future version?
|
No, this is not possible at the moment. As a workaround you could define one logbook per user, then restrict the user access to the individual logbooks. Of course this only makes sense if there are not too many users. |
|
Deamon on Debian, posted by Marco Rojas on Wed Jun 2 18:46:32 2010
|
Hi,
I have been using ELOG for a while and I love it. It is a default installation on Debian Lenny and ELOG 2.7.8. I am having problems with the deamon script, I can stop the service by doing /etc/init.d/elog stop but I can't started. When I do /etc/init.d/elog start I get this error: "Starting ELOG daemon: elogdCannot open "elogd.cfg": No such file or directory"
Somewhere there is a bad path to the elogd.cfg which is in "/usr/local/elog"
I would appreciate any help I can get.
Thank you.
Here is the scrip:
[code]
#!/bin/sh
# Init script for ELOG.
# Recai Oktas <roktas@omu.edu.tr>
PATH=/sbin:/bin:/usr/sbin:/usr/local/bin
DAEMON=/usr/local/sbin/elogd
NAME=elogd
DESC="ELOG daemon"
# Always run as daemon.
ARGS="-D"
# Admin might change some command line options without touching this script.
if [ -f /etc/default/elog ]; then
. /etc/default/elog
fi
test -f $DAEMON || exit 0
set -e
case "$1" in
start)
echo -n "Starting $DESC: $NAME"
start-stop-daemon --start --quiet --pidfile /var/run/$NAME.pid \
--exec $DAEMON -- $ARGS >/dev/null
echo "."
;;
stop)
echo -n "Stopping $DESC: $NAME"
start-stop-daemon --oknodo --stop --quiet --pidfile /var/run/$NAME.pid \
--exec $DAEMON -- $ARGS >/dev/null
echo "."
;;
reload)
# Do nothing since ELOG daemon responds to
# the changes in conffile directly.
;;
restart|force-reload)
echo -n "Restarting $DESC: $NAME"
start-stop-daemon --stop --quiet --pidfile \
/var/run/$NAME.pid --exec $DAEMON -- $ARGS >/dev/null
sleep 1
start-stop-daemon --start --quiet --pidfile \
/var/run/$NAME.pid --exec $DAEMON -- $ARGS >/dev/null
echo "."
;;
*)
N=/etc/init.d/$NAME
echo "Usage: $N {start|stop|restart|reload|force-reload}" >&2
exit 1
;;
esac
exit 0
[/code] |
|
Re: Deamon on Debian, posted by Stefan Ritt on Tue Jun 8 09:21:16 2010
|
| Marco Rojas wrote: |
|
Hi,
I have been using ELOG for a while and I love it. It is a default installation on Debian Lenny and ELOG 2.7.8. I am having problems with the deamon script, I can stop the service by doing /etc/init.d/elog stop but I can't started. When I do /etc/init.d/elog start I get this error: "Starting ELOG daemon: elogdCannot open "elogd.cfg": No such file or directory"
Somewhere there is a bad path to the elogd.cfg which is in "/usr/local/elog"
I would appreciate any help I can get.
Thank you.
Here is the scrip:
[code]
#!/bin/sh
# Init script for ELOG.
# Recai Oktas <roktas@omu.edu.tr>
PATH=/sbin:/bin:/usr/sbin:/usr/local/bin
DAEMON=/usr/local/sbin/elogd
NAME=elogd
DESC="ELOG daemon"
# Always run as daemon.
ARGS="-D"
# Admin might change some command line options without touching this script.
if [ -f /etc/default/elog ]; then
. /etc/default/elog
fi
test -f $DAEMON || exit 0
set -e
case "$1" in
start)
echo -n "Starting $DESC: $NAME"
start-stop-daemon --start --quiet --pidfile /var/run/$NAME.pid \
--exec $DAEMON -- $ARGS >/dev/null
echo "."
;;
stop)
echo -n "Stopping $DESC: $NAME"
start-stop-daemon --oknodo --stop --quiet --pidfile /var/run/$NAME.pid \
--exec $DAEMON -- $ARGS >/dev/null
echo "."
;;
reload)
# Do nothing since ELOG daemon responds to
# the changes in conffile directly.
;;
restart|force-reload)
echo -n "Restarting $DESC: $NAME"
start-stop-daemon --stop --quiet --pidfile \
/var/run/$NAME.pid --exec $DAEMON -- $ARGS >/dev/null
sleep 1
start-stop-daemon --start --quiet --pidfile \
/var/run/$NAME.pid --exec $DAEMON -- $ARGS >/dev/null
echo "."
;;
*)
N=/etc/init.d/$NAME
echo "Usage: $N {start|stop|restart|reload|force-reload}" >&2
exit 1
;;
esac
exit 0
[/code]
|
Unfortunately the Debian distribution was not done by me, so I only can guess:
- Is the executable existing under /usr/local/sbin/elogd ?
- In the start) section, I cannot find any reference to /usr/local/elog, so you maybe need something like
ARGS="-D -c /usr/local/elog/elogd.cfg"
|
cannot start elog, posted by harley on Thu May 27 22:35:49 2010
|
I have v2.7.7 of elog running on a OSX system running 10.6 I configured and installed about a year ago. It's a wonderful thing to have.
I acquired another system running 10.6 to dedicate to the elog app. I downloaded 2.7.8 and performed the following steps:
extract tarball in the desired directory
run
tar -xzvf elog-x.x.x.tar
switch to the new elog-x.x.x directory edit Makefile and elogd.cfg files as needed
to create executables
run
make
to create directories & files
run
make install
When I try to execute elog as a daemon:
elogd -c ~vulcanstaff/ELOG-Workspace/elog/elogd.cfg -D
I get the following message:
-bash: elogd: command not found
I'm not understanding why elogd cannot be found. The same message occurs when I try to test the installation with elogd -p 8080 from the sbin directory where elogd is installed.
I'm using the same Makefile and elogd.cfg files that work on the old system. My elogd and elogd.cfg files appear to be in the correct directories indicated in the Makefile:
#############################################################
#
# Directories for installation, modify if needed
#
ifndef PREFIX
PREFIX = ~vulcanstaff/ELOG-Workspace
endif
ifndef MANDIR
MANDIR = $(ROOT)$(PREFIX)/man
endif
ELOGDIR = $(ROOT)$(PREFIX)/elog
DESTDIR = $(ROOT)$(PREFIX)/bin
SDESTDIR = $(ROOT)$(PREFIX)/sbin
RCDIR = $(ROOT)$(PREFIX)/etc/rc.d/init.d
# flag for SSL support
USE_SSL = 1
# flag for crypt() support
USE_CRYPT =
#############################################################
Again, this works on the old system. Perhaps I've looked at it for too long, but I can't figure out what's going on. Assistance is greatly appreciated.
-harley
|
|
Re: cannot start elog, posted by Stefan Ritt on Tue Jun 1 13:17:18 2010
|
| harley wrote: |
|
I have v2.7.7 of elog running on a OSX system running 10.6 I configured and installed about a year ago. It's a wonderful thing to have.
I acquired another system running 10.6 to dedicate to the elog app. I downloaded 2.7.8 and performed the following steps:
extract tarball in the desired directory
run
tar -xzvf elog-x.x.x.tar
switch to the new elog-x.x.x directory edit Makefile and elogd.cfg files as needed
to create executables
run
make
to create directories & files
run
make install
When I try to execute elog as a daemon:
elogd -c ~vulcanstaff/ELOG-Workspace/elog/elogd.cfg -D
I get the following message:
-bash: elogd: command not found
I'm not understanding why elogd cannot be found. The same message occurs when I try to test the installation with elogd -p 8080 from the sbin directory where elogd is installed.
I'm using the same Makefile and elogd.cfg files that work on the old system. My elogd and elogd.cfg files appear to be in the correct directories indicated in the Makefile:
#############################################################
#
# Directories for installation, modify if needed
#
ifndef PREFIX
PREFIX = ~vulcanstaff/ELOG-Workspace
endif
ifndef MANDIR
MANDIR = $(ROOT)$(PREFIX)/man
endif
ELOGDIR = $(ROOT)$(PREFIX)/elog
DESTDIR = $(ROOT)$(PREFIX)/bin
SDESTDIR = $(ROOT)$(PREFIX)/sbin
RCDIR = $(ROOT)$(PREFIX)/etc/rc.d/init.d
# flag for SSL support
USE_SSL = 1
# flag for crypt() support
USE_CRYPT =
#############################################################
Again, this works on the old system. Perhaps I've looked at it for too long, but I can't figure out what's going on. Assistance is greatly appreciated.
-harley
|
Some Linux systems don't have the current directory (".") in the search path, so you have to start it with
./elogd -c ....
or explicitly with
/usr/sbin/elogd -c ...
|
|
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 |
|
Re: attachment filename bug & Makefile issue, posted by Stefan Ritt on Tue May 18 16:40:15 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"
Arghh! Why did you choose such a filename? This is the ELOG internal file format, which is YYMMDD_HHMMSS_name.ext.
For internal reasons (mainly for synchronization) the system checks every file name, and if it contains 6 numbers
followed by a "_" followed by 6 other numbers it thinks it's a valid date/time and uses that. Your time is however
0.0.0000, that's why it gets converted to some date in 1999. Do you absolutely need this functionality? While I can
easily remove the interpretation of the date, it would break the synchronization functionality and I would have to
find some other method to pass the file date/time, which would be quite some work. So if it's not too important for
you, I would like to keep it as it is.
> 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
The original idea was that one outcomments the whole line, like
#USE_SSL = 1
which always worked, but I agree that your solution is more general, so I changed the official Makefile. Thanks for
that. |
|
Re: attachment filename bug & Makefile issue, posted by A. Martin on Thu May 20 04:33:07 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"
>
> Arghh! Why did you choose such a filename? This is the ELOG internal file format, which is YYMMDD_HHMMSS_name.ext.
> For internal reasons (mainly for synchronization) the system checks every file name, and if it contains 6 numbers
> followed by a "_" followed by 6 other numbers it thinks it's a valid date/time and uses that. Your time is however
> 0.0.0000, that's why it gets converted to some date in 1999. Do you absolutely need this functionality? While I can
> easily remove the interpretation of the date, it would break the synchronization functionality and I would have to
> find some other method to pass the file date/time, which would be quite some work. So if it's not too important for
> you, I would like to keep it as it is.
>
Thank you for your response.
I can certainly use another filename, but I'm curious why elog doesn't convert the filename "000000_000000_file.txt" to
"YYMMDD_HHMMSS_000000_000000_file.txt" when it gets uploaded. All other files are automatically prepended with this
string. Manually renaming the file and then editing the elog entry via text editor seems to fix the file.
thanks,
amartin |
|