similar to: significant digits (PR#9682)

SUMMARY: Specific problem: I'm regridding biomass-burning emissions from a global/unprojected inventory to a regional projection (LCC over North America). I need to have boundaries for Canada, Mexico, and US (including US states), but also Caribbean and Atlantic nations (notably the Bahamas). I would also like to add Canadian provinces and Mexican states. How to put these together? General

r-help lattice adepts: I have a question which is somewhat geospatial, so I posted to r-sig-geo rather than here: https://stat.ethz.ch/pipermail/r-sig-geo/2012-November/016757.html > summary: How to overlay a geographical map on each panel in a lattice > (or Trellis), e.g., of levelplot's? Note I am not inquiring about > creating choropleth maps[,] which Sarkar 2008 covers quite

Hi all, I have a network with about ~800. The network is a mix of tinc 1.0 and 1.1 nodes. It is gradually expanding for several years now. The problem is that at some point it seams the daemon can not handle the processing of the new connection and the edges. There are 3 major nodes in the system and every other node initially makes connection to one of them. Now after a lot of debugging

Hi, thank for getting back. I'll answer the questions, but I've already gave up on tinc and switch to zerotier-one. On 2020-07-27 5:10 p.m., borg at uu3.net wrote: > Hi. I have few questions out of curiosity.. Cant help for now with > your problem... > > What version is crashing? 1.1 or 1.0 ? 1.1 is crashing > > How your network is segmented..? > I use tinc myself

Full_Name: Scott Wilkinson Version: 2.3.1 OS: WinXP Pro Submission from: (NULL) (140.253.203.4) In the example below round() does not report to the specified number of digits when the last digit to be reported is zero: Compare behaviour for 0.897575 and 0.946251. Ditto for signif(). The number of sigfigs is ambiguous unless the reader knows this behaviour. Is this a bug or intended behaviour? Is

Hi, quick question about snapshot mounting: Were there changes in 3.12 that were not mentioned in the release notes for snapshot mounting? I recently upgraded from 3.10 to 3.12 on CentOS (using centos-release-gluster312). The upgrade worked flawless. The volume works fine too. But mounting a snapshot fails with those two error messages: [2017-11-13 08:46:02.300719] E

Hi, using Gluster 9.2 on debian 11 I'm trying to set up geo replication. I am following this guide: https://docs.gluster.org/en/main/Administrator-Guide/Geo-Replication/#password-less-ssh I have a volume called "ansible" which is only a small volume and seemed like an ideal test case. Firstly, for a bit of feedback (this isn't my issue as I worked around it) I had this

sighandler_t signal(int signum, sighandler_t handler); it's in the headers ok but the function seems to be missing. I seem to recall this working in older versions. linking... /home/mesa/boot/v86bios/main.c:411: undefined reference to `signal' main.o(.text+0x613): /home/mesa/boot/v86bios/main.c:412: undefined reference to `signal' ===== Jon Smirl jonsmirl@yahoo.com

Hi Richard, Thanks for posting this. This issues is caused as part of the regression in 3.12.0 version [1], and is already fixed in 3.12.3 [2] version (3.12.3 is tagged now with couple of more subdirectory mount related fixes). [1] - https://bugzilla.redhat.com/show_bug.cgi?id=1501235 [2] - https://review.gluster.org/#/c/18506/ If you don't want to change the versions, then please remove

Hi everyone, I can't figure out how to format numbers to have a certain number of significant figures (as opposed to decimal places) without using scientific notation and including trailing zeros if necessary. e.g. I would like to achieve the following: 0.800001 ---> 0.8000 123.4567 ---> 123.4 0.1234567 ---> 0.1234 7.654321 ---> 7.654 7654321 --->

Signaling using normal kill(2) is preserved, but the master now prefers to signal workers using a pipe rather than kill(2). Non-graceful signals (:TERM/:KILL) are still sent using kill(2), as they ask for immediate shutdown. This change is necessary to avoid triggering the ubf (unblocking function) for rb_thread_call_without_gvl (and similar) functions extensions. Most notably, this fixes

On Thu, Jul 25, 2019 at 03:19:23PM -0500, Eric Blake wrote: > This looks a bit funny until I read the docs at [1]. When using > kill(2), I'm used to the function call 'kill(pid, 0)' probing for > process existence. But on the command line, kill(1) has the behavior of > sending SIGTERM by default when you omit a signal number (and not > serving as a process existence

Hello All We?ve have a problem with cluster client mounts fail in mid run with this in the log glusterfsd.c:1332:cleanup_and_exit] (-->/lib64/libpthread.so.0(+0x7dc5) [0x7f640c8b3dc5] -->/usr/sbin/glusterfs(glusterfs_sigwaiter+0xe5) [0x7f640df4bfd5] -->/usr/sbin/glusterfs(cleanup_and_exit+0x6b) [0x7f640df4bdfb] ) 0-: received signum (15), shutting down. We?ve tried running debug but

Hello Gluster users: sorry for long post, I have run out of ideas here, kindly let me know if i am looking at right places for logs and any suggested actions.....thanks a sudden power loss casued hard reboot - now the volume does not start Glusterfs- 3.3.1 on Centos 6.1 transport: TCP sharing volume over NFS for VM storage - VHD Files Type: distributed - only 1 node (brick) XFS (LVM)

Hi, On a debian 9 client, ======== root at kvm01:/var/lib/libvirt# dpkg -l glusterfs-client 8><--- ii glusterfs-client 3.8.8-1 amd64 clustered file-system (client package) root at kvm01:/var/lib/libvirt# ======= I am trying to to do a mount to a Centos 7 gluster setup, ======= [root at glustep1 libvirt]# rpm -q glusterfs glusterfs-4.0.2-1.el7.x86_64

I look every now and then at RPy. It is not yet a Debian package as it had the odd problem here or there -- initially an Atlas interaction, currently something with long_jump() which cannot be found when R's dynamic library is loaded. [1] It is called R_eval.c: /* Abort the current R computation and signal a KeyboardInterrupt exception */ void interrupt_R(int signum) { interrupted = 1;

Hello everyone, I am searching and searching and can't find an answer. I try to register a sighandler in my extension's C code. But my sighandler is never called. Is there anything preventing extensions to receive signals? I register like this: [.. some code that works ..] // register the sigint listeners. if (signal(SIGTERM, killReceiver) == SIG_ERR) {

Kay Sievers wrote: > Hi, > this simple program compiled with klibc: > > #include <stdio.h> > int main(int argc, char* argv[]) > { > setenv("TESTENV", "happy", 1); > printf("TESTENV='%s'\n", getenv("TESTENV")); > } > > prints: > > ./env > TESTENV='(null)' > >

I'm hoping that someone here can point me the right direction to help me solve a problem I am having. I've got 3 gluster peers and for some reason glusterd sill not start on one of them. All are running glusterfs version 3.4.0-8.el6 on Centos 6.4 (2.6.32-358.el6.x86_64). In /var/log/glusterfs/etc-glusterfs-glusterd.vol.log I see this error repeated 36 times (alternating between brick-0

short copy from a kubectl describe pod... Events: FirstSeen LastSeen Count From SubObjectPath Type Reason Message --------- -------- ----- ---- ------------- -------- ------ ------- 5h 54s 173 kubelet, k8s-bootcamp-rbac-np-worker-6263f70 Warning FailedMount (combined from similar events): MountVolume.SetUp failed for volume "pvc-fa4b2621-7dad-11e7-8a44-062df200059f" : glusterfs: