Our IT dept is very strict. I'll have to see if I can get email out to a web based email service like yahoo. But they will not give each of my mechanics an email account here.

Thanks

 Word of warning about fake email addresses - if your system suddenly does start to send out messages to them, you'll start getting otherwise mysterious email messages back about being unable to deliver and other such comments.  I speak from experience - although in my case the puzzle was finding what was generating the messages in the first place (not elog, another program as it happened).

I suggest you also include

Suppress default = 3

in your configuration file, which also stops them being generated in the first place. 

Although I was unaware (or had totally forgotten) that there was a 'Suppress email button' as mentioned in the documentation.

I never thought that someone will not have an email address. One basic feature of ELOG is its automatic notification if there is a new entry, and that only works over email. It's like social networks, you cannot register for Facebook if you don't have an email address.

So if you absolutely want to omit this, just give a fake email address, like nobody@no.where. ELOG just checks if there is a "@" and a "." somewhere. 

How can I skip the need for an email address when registering and logging in? Our IT dept will not give an email address to each guy I want on the log.

 never mind. I figured it out I left the <  > in the password = line

Yes I do feel stupid.

Looking at some of the questions here this seems too newbie to even ask.

I want to set up a log book for my mechanics. I want them to each have a password to log in and enter what they do each day.

When I try to set up a password file it takes all the info, then when I hit save it says "server has been reset" and it will not log in. I have to remove the password = and restart the server.

[global]
port = 8080


[TFB]
Password file = <tfbpass>


Theme = default
Comment = TFB ENGINEERING
Attributes = Mechanic, Type of entry, Status, Subject
Attributes = Author, Status
Options Status = Completed, Incomplete, Notification only
Cell Style Status Completed  = background-color:green
Cell Style Status Incomplete  = background-color:red
Cell Style Status Notification only  = background-color:yellow



Options Mechanic= Jeff K, Arnaldo M, Bob L, Nathan P
Options Type of entry = Break Down, PM Repair, Building, FYI, Other
Options Status = Completed, Incomplete, Notification only, Other
Extendable Options = Category, Status,
Required Attributes = Mechanic, Type of entry, Category, Status,
Page Title = TFB Engineering - $subject
Reverse sort = 1
Quick filter = Date, Mechanic

 

Hi Louis,

I'm a little surprised by your comment that you use symlinks 'to store your logbooks elsewhere'.

I start the daemon with

 /usr/local/sbin/elogd -p 8080 -c /home/logbooks/elogd.cfg -d /home/logbooks

so that both my logbooks *and* the config file are both based on my preferred location, which is a subdirectory of /home.  No symlinks  OK, themes are elsewhere, but for backup purposes, that's a rather lesser issue. 

I have no idea why the default logbook location is /usr/local/elog/logbooks which does not strike me as a sensible location (at least on Slackware).  Maybe such an odd location was to force users to choose a better location...(the -d switch).

To all:

I use Slackware (currently 13, I hear there are some issues with 14 for programs I wish use), and I compile from the sources.  Usually from random svn versions as a general pain-in-the-neck for Stefan.  I've never had to make a [Slackware] package for distribution - I have issued patches and/or source distribution, depending on your point of view.  If someone can provide the advice, I'd certainly try and do a Slackware distribution, but I do have Real Work to do as well, so it may not be done immediately.  I think Ubuntu is fairly close to Slackware, not sure about Debian, which I *thought* was close to Red Hat.

Now I *do* understand what some of the other contributors to this thread are doing, as I do something similar for other programs that are now unmaintained and no longer compile with GCC4 or earlier.  The email program I use is a ten-year-old binary & libraries I compiled under Slackware 7 (if not, 4), and I copy the relivent binaries, libraries and dependances across when I upgrade the o/s.  Yes, one day it will fall down.  Three other programs I regularly use are similarly now 'legacy'.  My 'C' coding isn't up to the major changes apparently needed to allow them to compile again with a modern compiler.
 

The Debian init script contributed here has been working quite well for me for the last few Ubuntu versions. Unless you edit it, it sets the elog base directory to /etc  so that's where you have to put your themes dir, resources, .conf file, scripts, logbooks, etc. I use symlinks to actually store my logbooks elsewhere.

I would also vote for a sane deb package. Right now, when I upgrade ELOG, I don't even run make install, I just copy the compiled binaries to their respective directories (/usr/bin or /usr/sbin). The rest stays the same.