ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
69783
|
Mon Apr 15 17:53:23 2024 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | ELOG V3.1.3-793 | Re: Draft saved after ~15 minutes, then anything entered a few hours later is ignored | That's strange. If you edit a message, indeed a draft is saved every ten seconds or so when you keep typing. In our installations we keep an elog entry typically open for eight hours, then save it at the end of the shift, and everything works fine. Have you tried playing aournd with your config file, like "Restrict edit time" or so? Please also make sure you have the current elog version. I sse you have 3.1.3 which is quit old.
Celeste Torkzaban wrote: |
Hello,
I've noticed that many times, I start an elog and continue editing adding to a few hours later, then I submit and it deletes everything I entered after the last time a draft was saved. I paid more attention and saw that it saves a draft after about a few minutes, and if I wait too long before submitting, it doesn't let me re-save the draft. My workaround is to copy all text before I submit, so if it ignores whatever I entered after the last saved version, I can edit it and paste it back in. Is there a setting someplace that I can change to fix this problem?
Thanks!
|
|
69784
|
Mon Apr 15 18:05:27 2024 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Mac OSX | 3.1.5 | Re: Suggestion to update Mac OS X instructions in ELOG Administrator's Guide | 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.
|
|
|
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.
|
|
|
|
69786
|
Tue Apr 16 13:31:02 2024 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Mac OSX | 3.1.5 | Re: 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.
|
|
69787
|
Fri Apr 19 12:30:52 2024 |
| Nick Sauerwein | nick.sauerwein@luxtelligence.ai | Info | Linux | 3.1.4 | Re: Extendable list of numeric items | Hey eloggers,
does anyone have an answer to this question?
Thanks for the help.
Best,
Nick
> Hey,
>
> thanks for your answer. I completely get your point. However, I think my question as not precise enough.
>
> I would like to have a numeric input, but many at the same time. When I make a new post, I would like to have an attribute 'wafer_IDs' that specifies the list of wafers this
process has been performed with. So for a single post I would like to have a list like this:
>
> wafer_IDs = numeric value, numeric value, numeric value, extendable
>
> Note: I am not referring here to the option. The numeric values are freely chooses numbers, the only this that varies from post to post is the number of numeric values put.
>
> Let me make an example (If the attribute were a string this would be the equivalent):
>
> 1st post: A process that was run with 3 wafers (ID: 1000, ID: 1001 and ID: 1002):
> wafer IDs = 1000, 1001, 1002
>
> 2nd post: A process that is run with 2 wafers (ID: 1000 and ID: 1002):
> wafer IDs = 1000, 1002
>
> The string solves the issue, but is not as nice as having directly a list of integers.
>
> Thanks for your help!
>
> Best,
>
> Nick |
|