search for: _safely_

...replacement in my home storage server I accidentally removed the post-it with the disk number from my three 1TB disks before connecting them back to the corresponding SATA connector. The issue now is that I don''t know in which order they should be connected. Do any of you know how can I _safely_ bring the zpool on-line? I didn''t plugged''em in yet becasue I''m afraid of losing some valueable personal information. Thanks in advance. Leandro. Yahoo! Cocina Encontra las mejores recetas con Yahoo! Cocina. http://ar.mujer.yahoo.com/cocina/ --------------...

Hello, I am not sure if I am interfacing with C correctly and _safely_ or if there is a better way esp. with regards to terminating the "returned" array. I am trying to fill an int array with values whose actual size is determined in the C function and is always maximally as large as length(values). I also don't understand the purpose of $ab in the e...

...essage + errno to stderr? > >+ _exit (EXIT_FAILURE); > >+ } > >+ if (fcntl (s, F_SETFD, flags & ~FD_CLOEXEC) == -1) { > >+ perror ("fcntl: F_SETFD"); > >+ _exit (EXIT_FAILURE); > >+ } > > About all we can _safely_ do is let our _exit() status inform the > parent process that something failed, and let the parent process > print the error message. But even passing errno as the _exit() > value is not portable (GNU Hurd errno values are intentionally > larger than what fit in 8-bit returns that the...

...different thread holding the lock but stranded by the fork. > + _exit (EXIT_FAILURE); > + } > + if (fcntl (s, F_SETFD, flags & ~FD_CLOEXEC) == -1) { > + perror ("fcntl: F_SETFD"); > + _exit (EXIT_FAILURE); > + } About all we can _safely_ do is let our _exit() status inform the parent process that something failed, and let the parent process print the error message. But even passing errno as the _exit() value is not portable (GNU Hurd errno values are intentionally larger than what fit in 8-bit returns that the parent would see...

If the user calls nbd_kill_subprocess, we shouldn't kill the process again when we close the handle (since the process has likely gone and we might be killing a different process). --- lib/handle.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/lib/handle.c b/lib/handle.c index 2af25fe..5ad818e 100644 --- a/lib/handle.c +++ b/lib/handle.c @@ -315,6 +315,8 @@