Re: {id,rt}prio broken (at syscall level?)
On 29 Apr, Jake Burkholder wrote: Thanks, this should be fixed now. A break; was forgotten in some recent proc locking changes. I will test it after softdep_update_inodeblock: bwrite: got error 22 while accessing filesystem is fixed (I made a backup of / after reading the bugreport and before trying it myself). Bye, Alexander. -- I believe the technical term is Oops! http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
{id,rt}prio broken (at syscall level?)
Hi, -current from yesterday: ---snip--- (45) root@ttyp0 # idprio 31 /bin/sleep 10 idprio: idprio: Invalid argument (46) root@ttyp0 # rtprio 31 /bin/sleep 10 rtprio: rtprio: Invalid argument ---snip--- isdnd is also affected (if you use its rtprio keyword in isdnd.rc). Bye, Alexander. -- Press every key to continue. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: {id,rt}prio broken (at syscall level?)
Hi, -current from yesterday: ---snip--- (45) root@ttyp0 # idprio 31 /bin/sleep 10 idprio: idprio: Invalid argument (46) root@ttyp0 # rtprio 31 /bin/sleep 10 rtprio: rtprio: Invalid argument ---snip--- isdnd is also affected (if you use its rtprio keyword in isdnd.rc). Thanks, this should be fixed now. A break; was forgotten in some recent proc locking changes. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
