J. Bruce Fields
791234448d
nfsd: decode implementation id
...
Decode the implementation ID and display in nfsd/clients/#/info. It may
be help identify the client. It won't be used otherwise.
(When this went into the protocol, I thought the implementation ID would
be a slippery slope towards implementation-specific workarounds as with
the http user-agent. But I guess I was wrong, the risk seems pretty low
now.)
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
2019-07-03 20:54:03 -04:00
..
2014-07-08 17:14:27 -04:00
2018-01-22 20:13:07 -08:00
2017-11-02 11:10:55 +01:00
2019-07-03 17:52:09 -04:00
2017-11-02 11:10:55 +01:00
2017-11-02 11:10:55 +01:00
2019-07-03 17:52:08 -04:00
2017-11-02 11:10:55 +01:00
2019-04-24 09:46:35 -04:00
2018-10-29 16:58:04 -04:00
2017-11-18 11:22:04 -08:00
2017-11-02 11:10:55 +01:00
2017-11-02 11:10:55 +01:00
2017-11-02 11:10:55 +01:00
2015-07-20 14:58:46 -04:00
2019-05-21 10:50:46 +02:00
2017-11-02 11:10:55 +01:00
2017-11-02 11:10:55 +01:00
2019-07-03 17:52:50 -04:00
2017-11-02 11:10:55 +01:00
2017-11-02 11:10:55 +01:00
2019-04-05 19:57:24 -04:00
2019-04-24 09:46:35 -04:00
2016-06-24 12:11:52 -04:00
2019-05-15 18:21:43 -07:00
2019-04-24 09:46:35 -04:00
2019-05-03 11:01:38 -04:00
2019-05-15 18:21:43 -07:00
2019-05-15 18:21:43 -07:00
2019-07-03 20:54:03 -04:00
2019-07-03 20:54:03 -04:00
2019-07-03 17:52:09 -04:00
2019-07-03 17:52:50 -04:00
2019-07-03 17:52:50 -04:00
2018-08-09 16:11:21 -04:00
2018-02-08 15:18:32 -08:00
2018-08-09 16:11:21 -04:00
2019-04-24 09:46:35 -04:00
2019-04-24 09:46:35 -04:00
2017-11-02 11:10:55 +01:00
2019-07-03 20:54:03 -04:00
2017-11-02 11:10:55 +01:00
2017-11-02 11:10:55 +01:00
2015-10-23 15:57:29 -04:00
2018-04-03 15:08:15 -04:00
2019-07-03 17:52:09 -04:00
2019-04-24 09:46:35 -04:00
2018-04-03 15:08:16 -04:00
2019-07-03 20:54:03 -04:00
2018-09-25 20:34:54 -04:00
2018-04-03 15:08:16 -04:00