search for: _thousands_

Displaying 7 results from an estimated 7 matches for "_thousands_".

2017 Sep 15
3
0-client_t: null client [Invalid argument] & high CPU usage (Gluster 3.12)
..._t.c:324:gf_client_ref] (-->/lib64/libgfrpc.so.0(rpcsvc_request_create+0xf8) [0x7f382007e7e8] -->/lib64/libgfrpc.so.0(rpcsvc_request_init+0x7f) [0x7f382007b93f] -->/lib64/libglusterfs.so.0(gf_client_ref+0x179) [0x7f3820315e59] ) 0-client_t: null client [Invalid argument] This is repeated _thousands_ of times and is especially noisey when any node is running gluster volume set <volname> <option> <value>. and I'm unsure if it's related but in /var/log/glusterfs/glustershd.log: [2017-09-15 00:36:21.654242] W [MSGID: 114010] [client-callback.c:28:client_cbk_fetchspec] 0...
2015 Apr 22
1
alternate licensing for package data?
...ources to document > origins of datasets. That is generally a little silly as ... R itself > already enforces in the .Rd files. So for the packages where I had to do that > the README.sources effectively becomes a forward reference to the R docs. > But then again the ftp-masters review _thousands_ of packages and having to > help their workflow is a small burden. > > In general, nitpicky licensing issue have been discussed (to mindnumbing > length) on the debian-legal list. Those interested in the issue may want to > peruse or search the archive: > http://news.gmane.or...
2017 Sep 18
2
0-client_t: null client [Invalid argument] & high CPU usage (Gluster 3.12)
...>/lib64/libgfrpc.so.0(rpcsvc_request_create+0xf8) [0x7f382007e7e8] -->/lib64/libgfrpc.so.0(rpcsvc_request_init+0x7f) [0x7f382007b93f] -->/lib64/libglusterfs.so.0(gf_client_ref+0x179) [0x7f3820315e59] ) 0-client_t: null client [Invalid argument] >> >> >> This is repeated _thousands_ of times and is especially noisey when any node is running gluster volume set <volname> <option> <value>. >> >> and I'm unsure if it's related but in /var/log/glusterfs/glustershd.log: >> >> [2017-09-15 00:36:21.654242] W [MSGID: 114010] [client-c...
2017 Sep 18
0
0-client_t: null client [Invalid argument] & high CPU usage (Gluster 3.12)
...gt;/lib64/libgfrpc.so.0(rpcsvc_request_create+0xf8) [0x7f382007e7e8] > -->/lib64/libgfrpc.so.0(rpcsvc_request_init+0x7f) [0x7f382007b93f] > -->/lib64/libglusterfs.so.0(gf_client_ref+0x179) [0x7f3820315e59] ) > 0-client_t: null client [Invalid argument] > > > This is repeated _thousands_ of times and is especially noisey when any > node is running gluster volume set <volname> <option> <value>. > > and I'm unsure if it's related but in /var/log/glusterfs/glustershd.log: > > [2017-09-15 00:36:21.654242] W [MSGID: 114010] > [client-callback....
2015 Apr 22
3
alternate licensing for package data?
Martyn Plummer <plummerm <at> iarc.fr> writes: > > I think this is covered well by the CRAN repository policy: > http://cran.r-project.org/web/packages/policies.html > > The two key license requirements are that: > 1) CRAN must have a perpetual license to distribute the package > 2) The package license should be listed here: >
2017 Sep 25
0
0-client_t: null client [Invalid argument] & high CPU usage (Gluster 3.12)
...>/lib64/libgfrpc.so.0(rpcsvc_request_create+0xf8) [0x7f382007e7e8] -->/lib64/libgfrpc.so.0(rpcsvc_request_init+0x7f) [0x7f382007b93f] -->/lib64/libglusterfs.so.0(gf_client_ref+0x179) [0x7f3820315e59] ) 0-client_t: null client [Invalid argument] >> >> >> This is repeated _thousands_ of times and is especially noisey when any node is running gluster volume set <volname> <option> <value>. >> >> and I'm unsure if it's related but in /var/log/glusterfs/glustershd.log: >> >> [2017-09-15 00:36:21.654242] W [MSGID: 114010] [client-c...
2015 Apr 22
0
alternate licensing for package data?
...ad to write README.sources to document origins of datasets. That is generally a little silly as ... R itself already enforces in the .Rd files. So for the packages where I had to do that the README.sources effectively becomes a forward reference to the R docs. But then again the ftp-masters review _thousands_ of packages and having to help their workflow is a small burden. In general, nitpicky licensing issue have been discussed (to mindnumbing length) on the debian-legal list. Those interested in the issue may want to peruse or search the archive: http://news.gmane.org/gmane.linux.debian.devel.leg...