<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Thanks, Bruce, this change to limits.conf worked for me. <Ubuntu 22.04><br><br><div dir="ltr"><div dir="ltr"><span style="background-color: rgba(255, 255, 255, 0);">•••<br>𝙄𝙛 𝙮𝙤𝙪 𝙖𝙧𝙚 𝙙𝙧𝙞𝙫𝙞𝙣𝙜 𝙖 𝙋𝙤𝙧𝙨𝙘𝙝𝙚, 𝙩𝙝𝙖𝙣𝙠 𝙮𝙤𝙪 𝙛𝙤𝙧 </span></div><div dir="ltr"><span style="background-color: rgba(255, 255, 255, 0);">𝙢𝙤𝙫𝙞𝙣𝙜 𝙤𝙫𝙚𝙧, 𝙨𝙤 𝙩𝙝𝙖𝙩 𝙄 𝙘𝙤𝙪𝙡𝙙 𝙨𝙖𝙛𝙚𝙡𝙮 𝙥𝙖𝙨𝙨! </span></div><div dir="ltr"><span style="font-size: 17pt; background-color: rgba(255, 255, 255, 0);"><b><i>Arrivederci, rabbit • D</i></b>𝙖𝙩𝙨𝙪𝙣 </span><span style="font-size: 17pt; background-color: rgba(255, 255, 255, 0);">𝟮𝟰𝟬</span><span style="font-size: 17pt; background-color: rgba(255, 255, 255, 0);">𝙕 • </span><span style="font-size: 17pt; background-color: rgba(255, 255, 255, 0);">🐰</span></div></div><div dir="ltr"><br><blockquote type="cite">On Jan 4, 2023, at 05:17, Bruce O'Neel <bruce.oneel@pckswarms.ch> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><div>Hi,<br></div><div><br></div><div>In what has to be the most frustrating response, it works for me...<br></div><div><br></div><div>This would be on a Linux (Linux Mint 21.1) which is basically a Ubuntu 22.04.<br></div><div><br></div><div>So the message comes from <br></div><div><br></div><div>7859 sched_setscheduler(7859, SCHED_FIFO, [1]) = -1 EPERM (Operation not permitted)<br></div><div><br></div><div><br></div><div>which you can get by prepending<br></div><div><br></div><div>strace -f -o /tmp/zz.log yoursqueakcommandlinehere<br></div><div><br></div><div>and then look at zz.tmp<br></div><div><br></div><div>The number at the beginning is not so important. That EPERM is what triggers the message.<br></div><div><br></div><div>If it returns 0 then all was happy.<br></div><div><br></div><div>In my case putting exactly the file requested in place (owned by root, 644 permissions) fixes it.<br></div><div><br></div><div>One simple way you can check is to type the command<br></div><div><br></div><div>ulimit -r<br></div><div><br></div><div>if it returns 2 then the file was processed when you logged in.<br></div><div><br></div><div>Otherwise it returns the default of 0.<br></div><div><br></div><div>So it does not work for Tim and that means debugging pam. Hold on while I go roll around in nettles for a while without clothes, it is more fun and way less painful.<br></div><div><br></div><div>1. put the lines that you have in squeak.conf in /etc/security/limits.conf instead. Maybe your pam_limits setup does not read limits.d directory. Perchance does /etc/limits exist? Ah, you have an old system. Put the same lines in /etc/limits.<br></div><div>2. if that does not work, does the file /etc/pam.d/login exist? If so, does it seem to reference limits? Mine limits section looks like<br></div><div># Sets up user limits according to /etc/security/limits.conf<br></div><div># (Replaces the use of /etc/limits in old login)<br></div><div>session required pam_limits.so<br></div><div>3. So do you sit at the console of this ubuntu system? No, try logging in from the console and see if that works?<br></div><div>4. If you do not sit at the console, and can't sit at the console try just a ssh into the box. What then does ulimit -r show? Still 0?<br></div><div><br></div><div>At this point there should be one of two cases.<br></div><div><br></div><div>1. You never see ulimit -r showing 2 regardless of whether you login via ssh, the console, or how ever you login normally.<br></div><div><br></div><div>2. You see ulimit -r showing 2 but only sometimes, not when you login like you want to login.<br></div><div><br></div><div><br></div><div>If it is the the first case then somehow the pam_limits module is not working. I have not seen this but it is always possible. And I don't know how to fix this other than "start reading those horrid instructions about debugging pam." Do note that if you break pam you will no longer be logging in so have some recovery pre-planned in this case. I would strongly recommend just redirecting stderr to some file in /tmp and ignoring the problem. It should only be annoying when your system is heavily loaded. <br></div><div><br></div><div>If it is case 2 then you are half in luck. You then need to figure out which one of the files in /etc/pam.d you are actually using rather than login and fixing that. My memory from the last time I had to play with this was that login was always run when you logged in, but, that could have changed....<br></div><div><br></div><div>Does this at least help somewhat?<br></div><div><br></div><div>cheers<br></div><div><br></div><div>bruce</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div class="ik_mail_quote answerContentMessage"><div>On 2023-01-04T02:09:10.000+01:00, tim Rowledge <tim@rowledge.org> wrote:</div><blockquote class="ws-ng-quote"><pre style="white-space: normal;">An aside that might trigger someone's memory - using the VM via a systemd unit file with 'LimitRTPRIO=2' appears to let the thread spawning do its thing.<br><br>In `top` with threads displayed I see - <br> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND <br> 1525 sagetea+ 20 0 176396 112684 7240 S 2.7 0.7 8:21.60 squeak <br> 1555 sagetea+ -2 0 176396 112684 7240 S 0.7 0.7 2:48.85 squeak <br><br>Whereas for a VM run 'normally'<br><br> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND <br> 4939 tim 20 0 266748 113184 7760 S 4.0 0.7 0:01.79 squeak <br> 4959 tim 20 0 266748 113184 7760 S 1.0 0.7 0:00.34 squeak <br> 4954 tim 20 0 266748 113184 7760 S 0.0 0.7 0:00.00 squeak <br> 4955 tim 20 0 266748 113184 7760 S 0.0 0.7 0:00.00 squeak <br><br><br>Which definitely looks different. Why the three threads? Why are two never showing anything under the TIME column? <br><br><blockquote class="ws-ng-quote"> On 2023-01-03, at 4:50 PM, tim Rowledge <<a target="_blank" class="defaultMailLink" href="mailto:tim@rowledge.org">tim@rowledge.org</a>> wrote:<br> <br> <br> <br><blockquote class="ws-ng-quote"> On 2023-01-03, at 4:40 PM, David T. Lewis <<a target="_blank" class="defaultMailLink" href="mailto:lewis@mail.msen.com">lewis@mail.msen.com</a>> wrote:<br> <br> On Tue, Jan 03, 2023 at 03:35:37PM -0800, tim Rowledge wrote:<br><blockquote class="ws-ng-quote"> This has been annoying me for some time but since I'm waiting for yet another TestRunner run I have a moment to whine about it.<br> <br> On my Pi I have no problems with the /etc/security/limits.d/squeak.conf file. Well, none that I know of. If I run a system from commandline there is no complaint about it.<br> <br> On my x86 ubuntu machine I created the file. It has the same permissions as on the pi, and the same content, and the owner in both cases is root. If I run a system from a commandline the first thing I see is a complaint about needing the damn file!<br> <br> What can I do to solve this? Is it simply the VM code being mistaken? Is there some other ubuntu related security dance we have to do?<br> <br></blockquote> <br> Log out completely from your shell session, and then log back in. <br></blockquote> <br> Oh, done that many times with no change in result :-(<br> <br><blockquote class="ws-ng-quote"> <br> If that doesn't work, unplug the computer and wait for the disk drive<br> to come to a complete halt, wait another 30 seconds, then plug it back<br> in and see if it starts working. Just kidding, kinda.<br></blockquote> <br> Tried that several times too. This is really weird.<br> <br> <br> tim<br> --<br> tim Rowledge; <a target="_blank" class="defaultMailLink" href="mailto:tim@rowledge.org">tim@rowledge.org</a>; <a target="_blank" class="defaultMailLink" href="http://www.rowledge.org/tim">http://www.rowledge.org/tim</a><br> APATHY ERROR: Don't bother striking any key.<br> <br> <br></blockquote> <br><br>tim<br>--<br>tim Rowledge; <a target="_blank" class="defaultMailLink" href="mailto:tim@rowledge.org">tim@rowledge.org</a>; <a target="_blank" class="defaultMailLink" href="http://www.rowledge.org/tim">http://www.rowledge.org/tim</a><br>Do you like me for my brain or my baud?</pre></blockquote></div>
<span></span><br></div></blockquote></body></html>