Ok, I fixed this in the current GIT version. You might check if that works for you.

Unfortunately this is not possible at the moment. You would have to use the menu command "copy to" and enable it for the admin user. Then you create your entry, and click on "copy to" once for each location you want to copy this entry.

I found a way to get this to work.  Define a "Messages" logbook for the messages to be broadcast.  None of the user installations need access to it. Use "Execute new = " to execute a script calling the elog command line client passing the message on to each target logbook.  Example:

--- elogd.cfg snippet begin ---

[Messages]

...

Execute new = mass_post.sh $text &

--- elogd.cfg snippet end ---

--- mass_post.sh begin ---

#!/bin/sh

elog -a Sender="System Administrator" -l "Logbook 1" $@

elog -a Sender="System Administrator" -l "Logbook 2" $@

elog -a Sender="System Administrator" -l "Logbook 3" $@

--- mass_post.sh end ---

The $@ expands to all the command line arguments, so the $text field, with all its spaces, gets passed correctly.  Sorry I showed you the example in bash/linux rather than in Windows, but I don't know Windows real well - you're better off translating into it yourself than my untested attempts.  The one thing I can tell you is that the "Execute new" command must include the "background fork".  In Linux this is provided by the & at the end of the line. In windows you'll need to use

Execute new = start "dummy" /min mass_post.bat

to background the process.  This is ESSENTIAL.  Without backgrounding the batch file, the elogd server will go into an infinite loop.  The parent process will wait for the child process to exit before continuing.  elogd is single-threaded, so the child process cannot start until the parent process has completed its current task (which is waiting for the child process to exit). 

You may need to tweak the above a little if you want to pass variable attributes to the script instead of defining them all in the script itself.

If I make "Email all" override the suppress email checkbox, some uses would complain "I check the supporess box, but my admin still gets email, what am I doing wrong here?". So while this works for you, it will not be desired for everybody. I would have to add another parameter just for this request. Couldn't you instead use the RSS feed functionality? This way you well see all entries, independent of the email notification. You can use special RSS feed readers (your browser and email client probably support this already).

Hmm, I see your point, but wouldn't using the RSS feed have the same effect? Or are you saying the users just wouldn't know about it, so they wouldn't complain? 

I haven't explored the RSS feed options yet. I'll study them.

The RSS feed you have to "pull" actively with a client (which of course can be periodically in an automatic way). So no pull, no notification, happy users

Hmm. Is there some way to set up a private RSS feed for me only?

If not, I would humbly ask that you add an option. I don't want to generate unnecessary email to users, but I need to always be notified for some logbooks. I'm responsible for some hardware on our project and I want to know any time someone reports a problem. The best solution is to still let users decide whether they want to subscribe to logbooks, and whether entry notification should be suppressed or not, but also have an admin override privilege. There could be a disclaimer "admin is automatically notified of all entries" at the top of the edit page.

If this can be done with a private RSS feed to me only, then that's fine. I still don't use or understand RSS feeds very well, sorry. I'd rather all users did not have the option to be alerted to every new entry, when email suppression is enabled. That would be contradictory, I think.

 Thanks for listening!

The RSS feed is private by default. You install a client (like Sharp Reader under Windows). It stays in the icon tray and periodically checks for new ELOG entries. If there is one, it pops up a window similar to your email client. You click on it, and it shows all entries like this:

 All you have to do is to enter the URL of the ELOG logook. Just add "elog.rdf" to the URL of the logbook as you would access it from your browser.

Here is the pop-up I got from writing just this entry: