search for: nerr

Hello, I have the same error, server is auto rebooted during every boot with kernel XEN, HS20 with Debian Wheezy and XEN hang on and AMM managment show same errors described in previous mails. With Debian wheezy wit non-xen kernel boots correcte, it seems that problems is with xen kernel Same Server HS20 with Debian Lenny+ XEN 3.2 or Debian Squeeze+XEN 4.0 working perfect Upgraded to Debian

Hello, Iam facing a problem in locking of files across samba shares. We have samba 3.0.10 running on Solaris 9 with the smb.conf as follows. # Global parameters [global] workgroup = NMUINT netbios name = NMUINTFS interfaces = <IP> bind interfaces only = Yes security = DOMAIN password server = XXX.XXX.XXX.XXX log level = 1 ldap

...xyModule = 0; return -3; } return 1; } int unloadDll() { m_ProxyObject->vtbl->release (m_ProxyObject); m_ProxyObject = 0; DWORD err; int b = FreeLibrary (m_ProxyModule); if (b==0) { err = GetLastError(); char ss[100]; sprintf(ss,"\n\nErr = %d\n\n", err); OutputDebugString(ss); return -1; } else OutputDebugString("no error unloading Rproxy dll.\n\n"); m_ProxyModule = 0; return 1; } int main() { char ss[100]; int i,x,a; for (i=1; i<=100; i++) { sprintf(ss,"Iteration: %d", i); Out...

This kind of fixes the problems in v1. The exception still primarily lives in the libnbdmod and you could still refer to it using libnbdmod.Error (but don't do that). However when the exception is printed it now appears as nbd.Error, and you can catch it also using the same name. Other problems: - There is no "nice" interface to accessing the exception fields. You have to use

...ranklin Street, Fifth Floor, Boston, MA 02110-1301 USA + +import nbd + +h = nbd.NBD () + +try: + # This will always throw an exception because the handle is not + # connected. + h.pread (0, 0) +except nbd.Error as ex: + str = ex.args[0] + errno = ex.args[1] + print ("str = %s\nerr = %d\n" % (str, errno)) + exit (0) + +# If we reach here then we didn't catch the exception above. +exit (1) -- 2.22.0

I spent a good few hours this morning trying to make this work and came up with the following patch. It's not quite right though. The exception I've created exists in the libnbdmod module (ie. the underlying C module that we use for the Python bindings). Ideally we'd define and throw an exception from the normal nbd module, but I couldn't work out how to do that. Probably

...line_offset = 0, first_line = 0, last_line = 0, first_column = 0, last_column = 0}, {nle = 0x0}}}, type = INDESC_INVALID, name = 0x0, {data = 0x0, fd = 0}, lineno = 0, column = 0, token_offset = 0, line_offset = 0} <repeats 15 times>}, indesc_idx = 0, msgs = 0x3cc19177d10, nerrs = 0, top_scope = {parent = 0x0, symbols = {next = 0x3cc191782c8, prev = 0x3cc191782c8}}, scopes = {0x3cc191782c0, 0x0, 0x0}, scope = 0, cmds = {next = 0x47a8a0c4d0, prev = 0x47a8a0c4d0}, ectx = {msgs = 0x3cc19177d10, cmd = 0x47a8a0c4d0, table = 0x0, rule = 0x0, set = 0x0, stmt = 0x0,...

This patch series introduces the tapback daemon, the user space daemon that acts as a device''s back-end, essentially most of blkback in user space. The daemon is responsible for coordinating the front-end and tapdisk. It creates tapdisk process as needed, instructs them to connect to/disconnect from the shared ring, and manages the state of the back-end. The shared ring between the