[PLUG] December PLUG meeting possibilities
GOOD NEWS: * We MIGHT have a speaker for the December PLUG talk. * We DO have a venue available. BAD NEWS: * The speaker we might have is me. I have been on an "ancient tape restoration adventure" over the last few months, and that might be a fun story and set of problems to demonstrate and talk about. * The Actually Exciting speaker I have partially-willing to talk has a very busy mail box and a classic (and presumed) mail box management technique is to just not worry about ignoring incoming emails, and I haven't heard a response from my recent ping and they almost certainly are not going to be available for December's meeting in (checks calendar) 5 days. QUESTION: "Excitement" and "Fun" are local phenomena, the intensity of which might vary significantly from person to person. Therefore, it is worth asking: * ARE YOU WILLING TO SIT THROUGH RUSSELL BLABBERING ABOUT HIS ANCIENT TAPES/TAPE DRIVES AND ASSOCIATED PROBLEMS? or * ARE YOU WILLING TO TALK YOURSELF INSTEAD, JUST TO AVOID HAVING TO LISTEN TO RUSSELL BLABBER? or * WOULD YOU PREFER A HOLIDAY-INFUSED UnPLUG? Please let me know your preference, either in a mailing list reply or to me privately. -- Russell Senior PLUG Volunteer russ...@pdxlinux.org
[PLUG-ANNOUNCE] December PLUG meeting possibilities
GOOD NEWS: * We MIGHT have a speaker for the December PLUG talk. * We DO have a venue available. BAD NEWS: * The speaker we might have is me. I have been on an "ancient tape restoration adventure" over the last few months, and that might be a fun story and set of problems to demonstrate and talk about. * The Actually Exciting speaker I have partially-willing to talk has a very busy mail box and a classic (and presumed) mail box management technique is to just not worry about ignoring incoming emails, and I haven't heard a response from my recent ping and they almost certainly are not going to be available for December's meeting in (checks calendar) 5 days. QUESTION: "Excitement" and "Fun" are local phenomena, the intensity of which might vary significantly from person to person. Therefore, it is worth asking: * ARE YOU WILLING TO SIT THROUGH RUSSELL BLABBERING ABOUT HIS ANCIENT TAPES/TAPE DRIVES AND ASSOCIATED PROBLEMS? or * ARE YOU WILLING TO TALK YOURSELF INSTEAD, JUST TO AVOID HAVING TO LISTEN TO RUSSELL BLABBER? or * WOULD YOU PREFER A HOLIDAY-INFUSED UnPLUG? Please let me know your preference, either in a mailing list reply or to me privately. -- Russell Senior PLUG Volunteer russ...@pdxlinux.org ___ PLUG: https://pdxlinux.org PLUG-announce mailing list PLUG-announce@lists.pdxlinux.org https://lists.pdxlinux.org/mailman/listinfo/plug-announce
Re: [PLUG] strange system behavior - inotify problem?
I suspect a clue to your issue is in your post, - see the following: https://stackoverflow.com/questions/639540/how-much-memory-can-a-32-bit-process-access-on-a-64-bit-operating-system I suspect that somewhere in that mess you might have a program that's not 64 bit clean. Just for grins try defining an 8GB ramdrive as your swapfile and I'll bet the freezing disappears. Ted -Original Message- From: PLUG On Behalf Of American Citizen Sent: Saturday, December 2, 2023 10:53 AM To: Portland Linux/Unix Group Subject: [PLUG] strange system behavior - inotify problem? Hello: I have a very interesting problem occurring my opensuse Leap 15.5 linux system. I am crunching number theory modules, using magma to do descents on elliptic curves. I do open a new konsole screen and do a tail on the magma results, in real time. There are 6 magma programs executing in this way at the same time. I also have 3 monitoring programs, but they are set up as a bash script file with a while [ 1 ] loop, but each has a sleep nnn seconds at the end of the loop. I was getting occasionally the tail warning message, no files left for tail, using polling instead. I installed the inotify-comment bash script from the stackexchange web page https://unix.stackexchange.com/questions/15509/whos-consuming-my-inotify-resources. Running this script does not show anything unusual, I am only using 402 watches in 131 instances. I did up the values in the sysctl.conf file to large sizes, so I don't suspect that the problem is caused by this. The system strangely halts the start of a new process, for up to 20 secs at a time, for example, I tried to open up a new Konsole screen and the window opens up, but then sits there for a period of time before completing the interior of the screen. Another example, while typing this email, I made a mistake and had to back up, the moment I hit the backspace key, everything froze for about 10 secs or so, before resuming. Third example, one of my monitoring screens suddenly went into uninterruptable mode, trying using control-C did not work, I had to terminate the Konsole screen and restart the bash script over again in a new window. Right now I don't know quite what to do? This is slowing things way down for me, while the system seems fine, I am only using 4 gigs of the 32 gigs system RAM, so that should not be a problem. Puzzled - Randall
[PLUG] strange system behavior - inotify problem?
Hello: I have a very interesting problem occurring my opensuse Leap 15.5 linux system. I am crunching number theory modules, using magma to do descents on elliptic curves. I do open a new konsole screen and do a tail on the magma results, in real time. There are 6 magma programs executing in this way at the same time. I also have 3 monitoring programs, but they are set up as a bash script file with a while [ 1 ] loop, but each has a sleep nnn seconds at the end of the loop. I was getting occasionally the tail warning message, no files left for tail, using polling instead. I installed the inotify-comment bash script from the stackexchange web page https://unix.stackexchange.com/questions/15509/whos-consuming-my-inotify-resources. Running this script does not show anything unusual, I am only using 402 watches in 131 instances. I did up the values in the sysctl.conf file to large sizes, so I don't suspect that the problem is caused by this. The system strangely halts the start of a new process, for up to 20 secs at a time, for example, I tried to open up a new Konsole screen and the window opens up, but then sits there for a period of time before completing the interior of the screen. Another example, while typing this email, I made a mistake and had to back up, the moment I hit the backspace key, everything froze for about 10 secs or so, before resuming. Third example, one of my monitoring screens suddenly went into uninterruptable mode, trying using control-C did not work, I had to terminate the Konsole screen and restart the bash script over again in a new window. Right now I don't know quite what to do? This is slowing things way down for me, while the system seems fine, I am only using 4 gigs of the 32 gigs system RAM, so that should not be a problem. Puzzled - Randall
