Re: Another potential ksh bug?

2020-12-07 Thread Noth
On 07/12/2020 05:41, Jordan Geoghegan wrote: Hello again, I was playing around with ksh array syntax and its behaviour when set as read-only. In my testing I noticed that ksh will allow you to overwrite the first element of a read-only array. Example snippet: #!/bin/ksh arr[0]=val1

Re: Another potential ksh bug?

2020-12-07 Thread Vadim Zhukov
For me, this is a definite bug. I've opted my students to fix this bug, so unless there's a hurry, there must be a fix till the end of December. :) пн, 7 дек. 2020 г. в 07:43, Jordan Geoghegan : > > Hello again, > > I was playing around with ksh array syntax and its behaviour when set as >

Re: pflogd write /var/run/mypflogdinstance.pid?

2020-12-07 Thread Theo de Raadt
Yep. It is possible we need a better strategy --- like placing *all* original argv in the [priv] title. trondd wrote: > Stuart Henderson wrote: > > > On 2020-12-07, Harald Dunkel wrote: > > > About the PIDs: Maybe a systctl like > > > > > > kernel.pid_max = 4194303 > > > > > > known from

Re: pflogd write /var/run/mypflogdinstance.pid?

2020-12-07 Thread trondd
Stuart Henderson wrote: > On 2020-12-07, Harald Dunkel wrote: > > About the PIDs: Maybe a systctl like > > > > kernel.pid_max = 4194303 > > > > known from other OSes could help to reduce the risk for PID conflicts. > > This doesn't help if you actually want reliability, rather than just >

Re: pflogd write /var/run/mypflogdinstance.pid?

2020-12-07 Thread Theo de Raadt
Stuart Henderson wrote: > On 2020-12-07, Harald Dunkel wrote: > > About the PIDs: Maybe a systctl like > > > > kernel.pid_max = 4194303 > > > > known from other OSes could help to reduce the risk for PID conflicts. > > This doesn't help if you actually want reliability, rather than just >

Re: clock not set on boot

2020-12-07 Thread Maurice McCarthy
On 05/12/2020, Patrick Wildt wrote: > > -s doesn't exist anymore. > ... and other replies... You've all proved what I guess I already knew. I don't live in the world anymore. It just passes me by.

Re: pflogd write /var/run/mypflogdinstance.pid?

2020-12-07 Thread Stuart Henderson
On 2020-12-07, Harald Dunkel wrote: > About the PIDs: Maybe a systctl like > > kernel.pid_max = 4194303 > > known from other OSes could help to reduce the risk for PID conflicts. This doesn't help if you actually want reliability, rather than just "reliable most of the time". There were

Re: pflogd write /var/run/mypflogdinstance.pid?

2020-12-07 Thread Harald Dunkel
On 12/7/20 7:43 AM, Theo de Raadt wrote: We've put some work into making programs not damage their argv. If you provide a strong set of arguments to the programs you start, you may be able to pkill with a more fullsize pattern, increasing the accuracy. AFAICS pflogd rewrites the command