Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 298 of 808  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Icon Author Author Email Category OS ELOG Version Subjectdown
  69785   Tue Apr 16 13:20:01 2024 Reply Andreas Warburtonandreas.warburton@mcgill.caRequestMac OSX3.1.5Re: Suggestion to update Mac OS X instructions in ELOG Administrator's Guide

Hi Stefan, Thanks a lot for implementing the updated commands. I noted that there are a few typos that could cause people confusion if not fixed:

In one case, "launchctl" is misspelled.

Confusingly, I think the two lines containing the 'enable' and 'disable' commands use the contiguous text string "system/ch.psi.elogd" (no space), whereas the two lines containing the 'bootstrap' and 'bootout' commands use the phrase "system /Library/LaunchDaemons/ch.psi.elogd.plist" (note space after 'system').

Many thanks, Andreas W.

Stefan Ritt wrote:

 

Thanks for the info, I updated the adminguide.

Stefan

Andreas Warburton wrote:

Here's a more complete/correct set of the updated commands:

sudo launchctl enable system/ch.psi.elogd
sudo launchctl bootstrap system /Library/LaunchDaemons/ch.psi.elogd.plist 

sudo launchctl bootout system /Library/LaunchDaemons/ch.psi.elogd.plist
sudo launchctl disable system/ch.psi.elogd

Cheers,
Andreas

Andreas Warburton wrote:

The section of the ELOG Administrator's Guide https://elog.psi.ch/elog/adminguide.html describing how to build and install ELOG on a Mac OS X system has worked well for me for several years, even though there have been warnings that the "load" and "unload" subcommands of the "launchctl" command have been deprecated for some time.  After trying my luck again on a new Mac with the latest operating system, I encountered errors of the type "Load failed: 5: Input/output error" when attempting to follow these instructions.

After a bit of searching around, I used information at the page https://www.alansiu.net/2023/11/15/launchctl-new-subcommand-basics-for-macos/ to deploy the more current subcommands as follows:

sudo launchctl enable system/ch.psi.elogd
sudo launchctl bootstrap system /Library/LaunchDaemons/ch.psi.elogd.plist 

sudo launchctl disable system/ch.psi.elogd

Once the above can be verified, perhaps the instructions in the Administrator's Guide can be updated accordingly.

 

 

 

 

  69786   Tue Apr 16 13:31:02 2024 Reply Stefan Rittstefan.ritt@psi.chRequestMac OSX3.1.5Re: Suggestion to update Mac OS X instructions in ELOG Administrator's Guide

Thanks, fixed.

Stefan

Andreas Warburton wrote:

Hi Stefan, Thanks a lot for implementing the updated commands. I noted that there are a few typos that could cause people confusion if not fixed:

In one case, "launchctl" is misspelled.

Confusingly, I think the two lines containing the 'enable' and 'disable' commands use the contiguous text string "system/ch.psi.elogd" (no space), whereas the two lines containing the 'bootstrap' and 'bootout' commands use the phrase "system /Library/LaunchDaemons/ch.psi.elogd.plist" (note space after 'system').

Many thanks, Andreas W.

  1625   Tue Jan 24 22:52:48 2006 Reply Stefan Rittstefan.ritt@psi.chRequestLinux2.6.1Re: Suggestion additional ElCodes

T. Ribbrock wrote:
However, there are two things I'm missing:
  • Headings
    It would be great to have a range of [H1][/H1], [H2][/H2], ... tags that map directly to their HTML counterparts (and have buttons, of course... Big grin ). That makes structuring an entry much easier in my opinion (and the output is easier to deal with for tools like html2ps) and I'm really missing those.
  • Tables
    This one is probably more difficult to add, but support for simple tables would be enough. But this is more a "nice to have"...


Yes, I missed tables myself already. The headings I just put into the current SVN version (see this forum for how it works). Tables are a bit harder to implement and will come later. Do you have a proposal for a possible syntax? A 1:1 relation to HTML would look like this:

[tr][th]heading1[/th][th]heading2[/th][/tr] [tr][td]data1[/td][td]data2[/td][/tr]


But that does not look very sexy to me. Maybe somehting like

heading 1 heading 2 heading 3
data 1 data 2 data 3


this looks a bit like the "pipe" mode from a Wiki

what do you think?
  1630   Wed Jan 25 12:31:14 2006 Reply T. Ribbrockemgaron@gmx.netRequestLinux2.6.1Re: Suggestion additional ElCodes

Stefan Ritt wrote:

Yes, I missed tables myself already. The headings I just put into the current SVN version (see this forum for how it works).


Very nice, thanks! I'm a bit torn as to whether I like the way I have to enter the level by keyboard or whether I'd rather see something like with the smileys (i.e. some "level menu" opens once "H" is pressed). The former is faster, while the latter doesn't require moving between the mouse and the keyboard. But that's just a detail - not really that important.


Stefan Ritt wrote:
Tables are a bit harder to implement and will come later. Do you have a proposal for a possible syntax?
[...]
Maybe somehting like

heading 1 heading 2 heading 3
data 1 data 2 data 3


this looks a bit like the "pipe" mode from a Wiki

what do you think?

Yup, I remember using that kind of "pipe" structure in Wikis and I actually liked it. I think it's a lot easier to read in the "source" as well - and it reminds me remotely of LaTeX... Wink Also, it doesn't require much to just type it out instead of using buttons to make the cells. Definitely good enough for the simple type of tables I had in mind!
  1897   Tue Aug 15 13:04:21 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.2Re: Substitutions in "Email all" do not work

Ben Shepherd wrote:
Email All = $Cc


Substitution was not enabled for email addresses, but I added this for you. It's in SVN revision 1712 if you build elog yourself from the SVN, otherwise it will be contained in the next release.
  1898   Tue Aug 15 13:07:52 2006 Reply Ben Shepherdbjs54@dl.ac.ukQuestionLinux2.6.2Re: Substitutions in "Email all" do not work

Stefan Ritt wrote:

Ben Shepherd wrote:
Email All = $Cc


Substitution was not enabled for email addresses, but I added this for you. It's in SVN revision 1712 if you build elog yourself from the SVN, otherwise it will be contained in the next release.


Great! Thanks very much. And quick too! Any idea when the next release will be available? Is there a mailing list I can sign up to to get notifications?
  1899   Tue Aug 15 13:09:18 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.2Re: Substitutions in "Email all" do not work

Ben Shepherd wrote:

Stefan Ritt wrote:

Ben Shepherd wrote:
Email All = $Cc


Substitution was not enabled for email addresses, but I added this for you. It's in SVN revision 1712 if you build elog yourself from the SVN, otherwise it will be contained in the next release.


Great! Thanks very much. And quick too! Any idea when the next release will be available? Is there a mailing list I can sign up to to get notifications?


You are on the mailing list Wink, there is only this list. But you can check out the SVN version as described in the documentation.
  66853   Wed Jul 21 16:38:05 2010 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.7.8Re: Subst variables and Execute

soren poulsen wrote:

Hi

 

I am trying to use this line from the documentation:

Execute new = echo "New message wiht ID $message id of type $type from $long_name on $remote_host" >> /tmp/elog.log

It does not seem to have the intended effect (of printing a line with the message id, etc in the file /tmp/elog.log
)

How can I make this line work ?

Soren

Have you started the server with the "-x" flag as written in the documentation? 

ELOG V3.1.5-3fb85fa6