/usr/bin/install -m 0755 -d /usr/local/bin /usr/local/sbin /usr/local/man/man1/ /usr/local/man/man8/
/usr/bin/install -m 0755 -o bin -g bin elog elconv /usr/local/bin
install: bin: Invalid argument
make: *** [install] Error 67

ifeq ($(OSTYPE),darwin)
CC = cc
endif

diff Makefile.darwin Makefile.origin
====================================
24,25d23
< BINOWNER = bin
< BINGROUP = bin
30,31d27
< OSTYPE = $(shell uname)
<
40,43d35
< ifeq ($(OSTYPE),Darwin)
< OSTYPE=darwin
< endif
<
46,47d37
< BINOWNER = root
< BINGROUP = admin
89,90c79,80
<       $(INSTALL) -m 0755 -o ${BINOWNER} -g ${BINGROUP} elog elconv $(DESTDIR)
<       $(INSTALL) -m 0755 -o ${BINOWNER} -g ${BINGROUP} elogd $(SDESTDIR)
---
>       $(INSTALL) -m 0755 -o bin -g bin elog elconv $(DESTDIR)
>       $(INSTALL) -m 0755 -o bin -g bin elogd $(SDESTDIR)

[IMG]elog:1/1[/IMG]

[IMG]elog:1/1[/IMG]

Dear all,

First, many thanks for creating and sharing this great tool which is ELOG! Our users are very happy with it!

I have few questions about inserting images into the entries.

From time to time our users insert them directly in the editor what leads to encoding the whole image in the HTML log file and the images does not appear in the attachments list. Saving and further editing of such entries slows down the whole ELOG server which uses 100% of CPU.

I'm not sure how they do it Ctrl+C & Ctrl+V, drag & drop, etc.. What I know is that if they add it using the "Insert image" action in the editor there are no problems and the images are properly listed in the attachments.

I read in the docs:

uploading or downloading an attachement file is a single request, and causes the entire file to be loaded in server memory while the request is being processed.
This is not normally a problem for the sort of short, text-mode entries ELOG is designed to support. However, if a user starts to upload or download a large attachment file (or image) over a slow link, all other users on that ELOG server will have to wait for that transfert to finish before they can access any logbook on that server. This is why there is a low limit on the size of attachments, and why ELOG should not be used to distribute large files under intensive multi-user conditions.

but I think this is not our case. Here I talk about wrongly inserting a single image of 700KiB.

So, I'm asking:

1. Is the behavior that we observe something already detected? If yes, which are exactly the wrong ways of inserting the images?
2. Is it fixed in newer ELOG versions?
3. Is it possible to disable the wrong ways of inserting the images in order to avoid such problems?

Many thanks in advance for your help!

Hi,

I have an eLog logbook installed on my machine.

If I click on the INSERT TIMESTAMP botton in this post a Timestamp of the kind "Wed Jul 29 23:09:15 2015" is added.

When I do the same (with the same browser) on my logbook, nothing is added. Ideas about what might be causing this?

Regards

Luca

Typing in a text for a new entry results in an error message, whenever
one forgets to fill in mandatory attributes (as it should happen !). However
after using the back button in this case (Using netscape 4.79) I made the
experience, that the text typed in gets lost. Other browsers like Mozilla
or IE do not have this problem. Any idea how this problem can be
avoided for netscape as well ?

elog: /1

Hello all,

I appear to be doing something wrong or not..
In my configuration I use an incrementation of a certain attribute (Melding)
For some weird reason it won't increment in this place, while it does in another place...

Below is my configuration (at least the part that gives me headaches..)

[Onderhoud Diversen]
Theme = default

Attributes = Melding, Auteur, Type, Planning, Categorie, Status, Onderwerp
Options Type = Preventief, Regulier, Nav Storing, Overig
Options Categorie = SensorProbes, Overig
Options Status = Wachtend, Gepland, In behandeling, Update, Afgerond
Type Planning = date
Extendable Options = Categorie, Status
Required Attributes = Auteur, Type, Unit-Lokatie, Status
Page Title = ELOG - $onderwerp
Reverse sort = 1
Quick filter = Date, Type, Status
Preset Melding= DIVOH: %d%m%y-####
Subst on edit Auteur = $long_name
List Display = ID, Melding, Datum, Status, Auteur, Type, Planning, Categorie, Onderwerp
Summary lines = 0
Display Email recipients = 0
Email All = aapie@sukkeltje.com
Use Email Subject = $Melding, $Onderwerp - $Status
Style Status In behandeling = background-color:red
Style Status Update = background-color:orange
Style Status Afgerond = background-color:lime
Login user = person1, person2

The goal of this part of the configuration is a way to notify and log maintenance on not specified equipment.
I expect a message-tag with: DIVOH: 280109-0001, where 280109 stands for 28th of January, 2009, the 0001 is the message number of that day.
Now when I enter something in it, submit the message it will display DIV-OH: 280109-0001 as I expect, but...
When I start with a new entry I would expect DIVOH: 280109-0002 as it is the second message.. Well, simply put.. I don't get DIVOH: 280109-0002 but instead I get DIVOH: 280109-0001 again.Below the part that does work correctly:

The following part of my configuration does work..

[Onderhoud Windows]
Theme = default

Attributes = Melding, Auteur, Type, Planning, Categorie, Status, Onderwerp
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Categorie = Algemeen, Hardware, Software, Netwerk, Telefonie, Overig
Options Status = Wachtend, Gepland, In behandeling, Update, Opgelost
Type Planning = date
Extendable Options = Categorie, Status
Required Attributes = Auteur, Type, Status
Page Title = ELOG - $onderwerp
Reverse sort = 1
Quick filter = Date, Type, Status
Preset Melding= WSOH: %d%m%y-####
Subst on edit Auteur = $long_name
List Display = ID, Melding, Datum, Status, Auteur, Type, Planning, Categorie, Onderwerp
Summary lines = 0
Style Status In behandeling = background-color:red
Style Status Update = background-color:orange
Style Status Afgerond = background-color:lime

When I copy this one, adjust it to be the same as the first one, but then without the extra things it doesn't work, and with them, well.. it still won't.. :(
I am at a loss here where the mistake is, can someone shed some light on this? I would appreciate that very much.

Best regards,

Guido

 

I may have missed it when reading the logs, if so, sorry about that, but I would like to know if there is a way to set a field, let us call it "process run"  Ok let me give you some details on this.

a process run may have several "work orders" or sets of parts/items in it, so it will have several separate entries in the log  such as:

date##, run123, part 1, quantity, comment

date##, run123, part2, quantity, comment

date##, run123, part3, quantity, comment

date##, run123, part4, quantity, comment

I thought perhaps to have them use the reply function to add the other 3 items of the same run, and that would work if I could find a way to set 'process run' to auto increment, say perhaps, when the next 'New' entry was entered.  Is there something in place that can already do this?  If this is possible, I thought I would see if I can change the button for 'New' to something like 'New Run' and reply to 'Add Workorder' or something along that line so there is no confusion when entering the data.

Any suggestions you might provide are greatfully accepted.

Chuck