Displaying 4 results from an estimated 4 matches for "87ms".
Did you mean:
  870s
  
2015 Aug 31
2
CentOS 7.1 NFS Client Issues - rpc.statd / rpcbind
...makes sense that this would not work.
If I enable nfs-server.service then rpcbind does really get started but 
I loathe to start this on all clients
Anyone have any ideas how to get rpcbind started before rpc.statd in a 
NFS client only config
root /root 103# systemd-analyze blame
        1min 87ms rpc-statd.service
root at ls2 /root 79# systemctl list-units | grep rpc
rpcbind.socket loaded active listening RPCbind Server Activation Socket
Aug 30 18:17:14 ls2.tokenrain.name systemd: Starting NFS status monitor 
for NFSv2/3 locking....
Aug 30 18:17:14 ls2.tokenrain.name rpc.statd[1938]: Vers...
2005 Nov 24
0
max latency with htb and wondershaper for voip and p2p
...hy is voip still choppy.
In my config, can I assume that packets in 1:10 have the highest 
priority even with htb? (if the 1:10 rate is not reached).
Do I need to setup a prio qdisc instead of htb for voip?
If I lower the mtu of the p2p software to 750byte for example, will I 
get a max latency of 87ms?
Can I do voip and P2P together with htb with such a line?
Thanks for your help.
     qdisc htb 1: r2q 1 default 20 direct_packets_stat 0
qdisc htb 1:      :       9637 ( 77.096000 kbit/s) sent=305656509  :
      Sent 305656509 bytes 1228041 pkts (dropped 0, overlimits 559094 
requeues 0)
     qd...
2015 Aug 31
0
CentOS 7.1 NFS Client Issues - rpc.statd / rpcbind
...gt;
> If I enable nfs-server.service then rpcbind does really get started 
> but I loathe to start this on all clients
>
> Anyone have any ideas how to get rpcbind started before rpc.statd in a 
> NFS client only config
>
> root /root 103# systemd-analyze blame
>        1min 87ms rpc-statd.service
>
> root at ls2 /root 79# systemctl list-units | grep rpc
> rpcbind.socket loaded active listening RPCbind Server Activation Socket
>
> Aug 30 18:17:14 ls2.tokenrain.name systemd: Starting NFS status 
> monitor for NFSv2/3 locking....
> Aug 30 18:17:14 ls2.tok...
2015 Aug 31
1
CentOS 7.1 NFS Client Issues - rpc.statd / rpcbind
...ver.service then rpcbind does really get started 
>> but I loathe to start this on all clients
>>
>> Anyone have any ideas how to get rpcbind started before rpc.statd in 
>> a NFS client only config
>>
>> root /root 103# systemd-analyze blame
>>        1min 87ms rpc-statd.service
>>
>> root at ls2 /root 79# systemctl list-units | grep rpc
>> rpcbind.socket loaded active listening RPCbind Server Activation Socket
>>
>> Aug 30 18:17:14 ls2.tokenrain.name systemd: Starting NFS status 
>> monitor for NFSv2/3 locking....
>...