Re: pf queue definition: bandwidth resolution problem

2017-05-13 Thread Mike Belopuhov
Good call. This one is a bit more complicated since we have 5 positions to display and the last one is sort of reserved for the unit specifier. So ignoring the unit we can display numbers from 1 to . However, when truncating numbers like that we have to properly round them. I've been taught

Re: pf queue definition: bandwidth resolution problem

2017-05-13 Thread Carl Mascott
One more thing: The BW column of "systat queues" has the same truncation error. I'm guessing that "systat queues" is running "pfctl -vsqueue" periodically, but if that's not the case then the same fix is needed in systat. On Sat, 5/13/17, Carl Mascot

Re: pf queue definition: bandwidth resolution problem

2017-05-13 Thread Carl Mascott
First, just to be safe, I did a bandwidth test with only one queue, max bandwidth 1999K. pf is fine: measured speed was about 2M. Just eyeballing it, I don't see anything wrong with your patch, but I have no way to test it: I'm not set up to build from source. If I understand correctly you have

Re: pf queue definition: bandwidth resolution problem

2017-05-13 Thread Mike Belopuhov
Ah, I see what you mean. Indeed, we have to make sure the remainder is 0 when we're displaying the bandwidth. I think the diff below is what we want. Works fine here, any OKs? On Sat, May 13, 2017 at 18:34 +, Carl Mascott wrote: > You missed the point. I didn't do any testing. I just looked

printcap(5) error

2017-05-13 Thread martin
printcap(5) says: NameTypeDefault Description sd str /var/spool/outputspool directory However as far as I can tell, the actual default is /var/spool/output/lpd. That's what's listed in usr.sbin/lpr/common_source/pathnames.h, and lpd behaves the same wi