I have tried to set Email Format = 111 but still receiving attachments in the notification emails.  Does anyone know how to configure?  So the notification email will not include attachments.

Thanks in advance,

H. Dao

I just tried and it works fine for me as expected. So you must so something wrong like:

- change the wrong elgod.cfg, 

- have a typo in your configuration

- have a too old version of elogd

Why don't you upgrade to the current version and try again? I forgot when I introduced this feature, but it might be after version 2.6 which you are using.

- Stefan 

 In a test area we loaded elogd 2.9.0 built Mar 21 2011, 08:48:02 revision 2396

During our testing we started the creation of a new elog, then backed out cancelling the creation and received the following error.

Error: Too many parameters (> 120). Cannot perform operation.

We do not see this error in the older version.

Hi

  I just updated my mirror server, which I just use as a backup to my main server, to 2.9.0 and found that after logging in (the selection page is not protected, but the individual logbooks are) and coming back to the selection page I no longer get the "Synchronize all logbooks" even though I am an admin user. The relevant code is in elogd.c in the show_selection_page() routine:

       /* only admin user sees synchronization link */
        if (is_admin_user("global", getparam("unm"))) {
         rsprintf("<tr>\n");
         rsprintf("<td colspan=13 class=\"seltitle\">\n");
         rsprintf("<a href=\"?cmd=Synchronize\">%s</a></td>\n", loc("Synchronize all logbooks"));
         rsprintf("</tr>\n");
      }
 

what is happening is that after logging in to a logbook and coming back to the selection page, the "unm" parameter is not set, so getparam("unm") returns NULL, who clearly is not in the admin user list.  The strange thing is that in an individual logbook the unm (and uname) parameters are working fine, and I have admin rights - can change the global config file, do an individual synchronization, etc.  It is just from the selection page that the unm parameter is not working.

In fact, I commented out the if statement above, just to see if I could get synchronized using the link, and that failed too, with a message "No user name supplied for remote access" even though I do have a "mirror user" statement in my config.  Again, if I do each one individually it all works.  In addition, the cron synchronization (i.e. mirror cron) also works fine.

Obviously this isn't crucial, just a pain that can be worked around, but if anyone has any ideas I'd be glad to hear them.

Steve

PS Another feature request: when you forget to set an icon in this forum and then use the "back button" it shouldn't force you to rewrite the whole message over again!

Is it possible to have many roots with one elogd (or run several elogds), such that you can seaparate different groups or themes from each other:

electronics

       trigger

       power

mechanics

       detector

       support

Thanks.

Christoph

Have a look at "top groups" in the documentation 

 Thanks. I got it working so far. One minor glitch:

I have one topgroup (with 2 subgroups),

  electronics

       trigger

       power

and onother topgroup (only 1 subgroup)

 mechanics

   detector

When I get the login screen for the second (with the only one subgroup) it says in the header:

   "Several logbooks are defined on this host. Please select the one to connect to:"

and below only the one group (detector)  is shown, so actually nothing to select.

This may be possibly achieved by not defining a subgroup for the second one and leaving it as a topgroup,

but I don't know how it behaves, when the group admin decides to create a subgroup. Can he do

without requiring superuser or elog permissions?

--

Christoph

Is there a way to setup a search, to search several log books but not all the logs books at one time?

Thanks

Carl

No. You can either search one logbook or all logbooks. There is however the way to have separate groups of logbooks, which are "invisible" from each other. Like running several elogd daemons at the same time. Then your search on all logbooks will only run on the logbooks of one group. Check the documentation for "top groups".

- Stefan

Hi,

I'm currently trying to setup a logbook which will contain process descriptions. One of the attributes will be the resists that are used. This could be more than one resist, hence I try to use MOptions but users should also be able to add materials to the selection list. When I write the following, I get some problems though:

Required Attributes = Name, Author, Resists
MOptions Resists =  Nano Copolymer EL-10, S1813
Extendable options = Resists

If a user wants to add a resist, he gets a textbox to add the new resist (which will contain what was already toggled), but there is now way to select also other resists that are already available, without saving the post and than edit it again. Previously selected resists are deselected when a new resist is added (if the user had emptied the textbox) and one can not save the newly added attribute option without saving the whole entry.

Is there a nice way to implement this (am I overlooking an obvious solution), or is this not possible at all. I guess an ideal solution would be to get some sort of ok button when one adds an attribute option and after confirming the new value that one gets back to the checkboxes without exiting the edit mode.

Regards,

Michaël

PS: This is the complete config for this logbook:

Theme = default
Page Title = $logbook - $Name
Edit Page Title = $logbook
Comment = Photolithography Processes

Quick filter = Name, Resists
Preset Author = $long_name
Reverse sort = 1

Attributes = Name, Author, Resists
Sort Attributes = Resists, Name, Author
Required Attributes = Name, Author, Resists
MOptions Resists =  Nano Copolymer EL-10, S1813
Extendable options = Resists
Sort Attribute Options Resists = 1

List display = Name, Author, Resists

If you use an attribute "Entry" then the internal variable "entry time" will expand to the last value of
"$Entry"+" time", e.g. if you use it in "Thread display = $entry time, ..."

One side effect is, that the logbook selection page defaults to use
Last submission = $entry time by $author
Which then expands to an undesired result.

This is not really a bug, rather something you'll need to keep in the back of your mind.

A query to a logbook can crash the demon.

Query:
https://pc8059.psi.ch:444/SwissFEL+Injector/?jcmd=Find&m0a=10&d0a=27&y0a=2011&npp=1&reverse=0

gdb dump:
SSLServer listening on port 444 ...

Program received signal SIGSEGV, Segmentation fault.
show_elog_list (lbs=0xae72618, past_n=0, last_n=0, page_n=0, default_page=1, info=0x0) at src/elogd.c:20797
20797         message_id = msg_list[index].lbs->el_index[msg_list[index].index].message_id;

I have a logbook with data in it that I need  to  rename  and preserve the the existing data (old book) in the newly named book (i.e. can I move all of the data from one book to a new book and than delete the data from the original book)?

As always thank you for your time.

There are two ways:

1) Create a new logbook, add the "Copy to" command to the old logbook. Select all entries and copy them to the new logbook, and delete the old one.

2) Change the logbook name in elogd.cfg, by manually editing the file, then rename the subdirectory in your file system from the old to the new name, then restart elogd.

The second solution is much simpler, but you have to manipulate files and directories yourself.

Whatever you do, make sure to back up you files before any operation. 

 Sorry, about this dumb question but with  "Copy to = <logbook list> " what is the format of  <logbook list>?

Is it just the "logbook Name" or is it the actual path name   "http://something/somethingelse"?

 In order to copy (or move) files from one logbook to another, you first need to ensure that  the
appropriate commands are in the section of elogd.cfg of the logbook the files move *from* (called 'current')

 - made up elogd.cfg to show this, and obviously only the pertinant lines

[Global]

Group = current, Y2011, Y2010, Y2009...

...

 [current]
...
Menu commands = New, ... Copy to, ...
...
Copy to = Y2011, Y2010, Y2009 ...
...
 - end of made up example.
 
So to solve your problem, the <logbook list> is simply the list of logbooks in
this part of elogd.cfg after the 'Copy to =' line in the elogd.cfg file (Y2011, Y2010, Y2009...)  

You also need to ensure that the directory to which the entries are to be copied to exists!

('Move to' would be faster if you are going to delete the entries in 'current' afterwards, but as always, it depends on

your perception of risk.)

For the user, the logbook list is the set of logbooks that appear in the
drop-down menu by the side of "Copy to" in the menu bar, and it allows you to
move that entry (or thread of entries if more than one) to the selected destination.

---

My reason for answering this is because I have actually done this operation 'in
anger' some time ago and regularly since, and would have answered before if Stafan had not beaten me
to it.  I used what was Stefan's second method, which, for those who are
reasonably confident with file manipulation, is far faster, and, dare I say,
less prone to 'unexpected' issues - some here will know what I'm
getting at.

So I say, "Back up your files and take the plunge", I would have put something
else but this is a family friendly forum.

But you must bear in mind my views are those seen through the filter of a
regular Elog ab-user, which may be why Stefan worked so hard to answer before
me ;-)

Anyway, Stefan <i>et al</i> have got CERN's faster-than-light particle problem to deal with this morning.

I would be too lucky if I just could fix this as I fix some ELOG problems! I guess hundreds of physicists right now are pondering about what could have gone wrong in data taking, because nobody really believes that this is a real effect. 

 Got it to work, manipulating the files was not that hard once I got over the FEAR factor.  Good luck with the speed of light thing.

 Well done Mike!

One result is that I've also learnt things, realised that there are some known unknowns and perhaps some unknown unknowns in my

understanding of Elog.