ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
69824
|
Sun Sep 1 04:33:13 2024 |
| Dominic | anonymous@gmail.com | Bug report | Linux | Windows | Mac OSX | ELOG V3.1.5 | Equation Editor does not work |
Hi!
I am not sure if this is a know issue: it seems that the equation editor does not work anymore. Is there any fix or alternative method to type latex formula in the log?
Thank you! |
1644
|
Thu Feb 2 03:19:44 2006 |
| Angus Au | angus_au@promina.com.au | Question | Other | 2.6.1 | compiling elog 2.6.1 on solaris platform |
I came across problem in compiling elog 2.6.1 on solaris platform.
The messages "
# make
gcc -o elog src/elog.c -lutil -lsocket -lnsl
ld: fatal: library -lutil: not found
ld: fatal: File processing errors. No output written to elog
collect2: ld returned 1 exit status
*** Error code 1
make: Fatal error: Command failed for target `elog'
It seems to me that library libutil does not exist on solaris platform.
Is there any fix ? I can compile elog 2.6.0 successfully on solaris. |
69752
|
Thu Mar 7 08:55:49 2024 |
| Andreas Warburton | andreas.warburton@mcgill.ca | Bug report | Mac OSX | 3.1.5-23df00d9 | Runaway bogus attachment counts in Summary view attachment column |
On a new MacBook Pro (Silicon M3), I installed version 3.1.5 build 23df00d9. The application appears to work normally, except that, after a short while, the indicated attachment count (paperclips in the attachment column of the Summary view) starts to increment fairly rapidly with each time that I visit the page. Attachment counts appear even for records that don't have any attachments. When I access records individually, either those with or without real attachments, everything looks OK. Any insights as to what might be causing this, and how to correct?
Installation went smoothly using the (now longstanding) MacOS installation instructions, with one small exception: When doing the "sudo launchctl load ..." step, there is occasionally an I/O error of some kind. (Sorry, I don't have an exact transcript of the error at the moment, but it appears to refer to line 5 of a script.)
Many thanks,
Andreas W. |
69755
|
Sat Mar 9 17:04:13 2024 |
| Andreas Warburton | andreas.warburton@mcgill.ca | Bug report | Mac OSX | 3.1.5-23df00d9 | Re: Runaway bogus attachment counts in Summary view attachment column |
A quick follow-up concerning the secondary matter I mentioned in my last post, namely the issues I had with the deprecated "sudo launchctl load ..." and "sudo launchctl unload ..." subcommands currently provided in the ELOG installation instructions for MacOS. I found a solution to this -- will post it in a separate thread.
The strangely auto-incrementing attachment counts in the Summary view are still present, and I'm curious if anyone else has experienced those. Also, I could not find a way to customize the Summary view such that the final (rightmost) column with the attachment counts can be suppressed. That would at least put the problem out of sight until a developer can intervene and fix the bug.
Andreas Warburton wrote: |
On a new MacBook Pro (Silicon M3), I installed version 3.1.5 build 23df00d9. The application appears to work normally, except that, after a short while, the indicated attachment count (paperclips in the attachment column of the Summary view) starts to increment fairly rapidly with each time that I visit the page. Attachment counts appear even for records that don't have any attachments. When I access records individually, either those with or without real attachments, everything looks OK. Any insights as to what might be causing this, and how to correct?
Installation went smoothly using the (now longstanding) MacOS installation instructions, with one small exception: When doing the "sudo launchctl load ..." step, there is occasionally an I/O error of some kind. (Sorry, I don't have an exact transcript of the error at the moment, but it appears to refer to line 5 of a script.)
Many thanks,
Andreas W.
|
|
69757
|
Sat Mar 9 17:17:02 2024 |
| Andreas Warburton | andreas.warburton@mcgill.ca | Request | Mac OSX | 3.1.5 | Suggestion to update Mac OS X instructions in ELOG Administrator's Guide |
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.
|
69758
|
Sun Mar 10 04:25:43 2024 |
| Andreas Warburton | andreas.warburton@mcgill.ca | Request | Mac OSX | 3.1.5 | Re: Suggestion to update Mac OS X instructions in ELOG Administrator's Guide |
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.
|
|
69785
|
Tue Apr 16 13:20:01 2024 |
| Andreas Warburton | andreas.warburton@mcgill.ca | Request | Mac OSX | 3.1.5 | Re: 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.
|
|
|
|
2091
|
Fri Nov 24 23:08:33 2006 |
| Andreas Warburton | andreas.warburton@gmail.com | Question | Linux | Windows | 2.6.2-1755 | Resubmit-as-new-entry behaviour when synchronizing/mirroring |
Hello,
I am running two ELOG installations: one on my Windows laptop; the other on a Debian linux web server. I have mirroring set up between the two installations. This has worked well for over a year. I am hoping that someone can help me regarding the following odd behaviour.
1. I edit (create) an entry on my Windows laptop. This entry gets mirrored or synchronized to the Linux machine.
2. I can view the entry fine both on the Windows side and on the Linux side.
3. I then edit the entry on the Linux side. After saving, the revised entry is visible on the Linux side.
4. I then have the same entry number available on both installations, but the two have different content due to my edit.
5. If I then synchronize, the original (unedited) entry is preserved along with the new entry, so both the Windows and Linux installations now have TWO entries each, representing the unedited and edited versions. The time stamps are identical, but the edited version is given a new ID number.
As a check, I explicitly added the line "Resubmit default = 0", which I know refers to editing and not synchronization, to my config file. The weird thing is that the synchronize/mirror operation seems to be acting with a "Resubmit default = 2" kind of behaviour.
Has anyone observed this happening?
Thanks for any comments or insights.
Cheers,
Andreas |