search for: 3a01

Displaying 3 results from an estimated 3 matches for "3a01".

Did you mean: 301
2000 Aug 15
1
Oplock problem in 2.0.7 locks up Samba completely
...ast occurrence of the problem), all Samba services lock up completely. The log is filled with messages like the follow- ing: [2000/08/14 09:49:14, 0] smbd/oplock.c:request_oplock_break(1204) request_oplock_break: no response received to oplock break request to pid 5060 on port 3708 for dev = 3a01, inode = 16484 for dev = 3a01, inode = 16484, tv_sec = 3997a286, tv_usec = c5bf0 [2000/08/14 09:49:46, 0] smbd/oplock.c:request_oplock_break(1204) request_oplock_break: no response received to oplock break request to pid 5060 on port 3708 for dev = 3a01, inode = 16484 for dev = 3a01, inode...
2006 Sep 08
4
Failed to create a solaris DOMU using NFS root
Hello, I''ve installed a OpenSolaris dom0 snv_44 on a x4100 server, and booted a 32-bit xen kernel. I''m trying to create a OpenSolaris DOMU (snv_44) by following the howto described at http://www.opensolaris.org/os/community/xen/howto/create-osox-domu/. I did not manage to create a diskless environment by using SUNWCXall. I''ve created SUNWCreq instead and add the
2012 Jul 27
0
Bug#682979: sample logfile
...eue = [ VM.start VM.start R:34d8075638bd ](1) [20120727T14:44:24.848Z|debug|vh10|1025||thread_queue] pop(vm_lifecycle_op) = VM.start VM.start R:34d8075638bd [20120727T14:44:24.848Z|debug|vh10|1023 UNIX /var/lib/xcp/xapi|VM.start R:34d8075638bd|locking_helpers] Acquired lock on VM OpaqueRef:4f326183-3a01-71cc-6cb0-96e3007694f9 with token 3 [20120727T14:44:24.848Z|debug|vh10|1023 UNIX /var/lib/xcp/xapi|VM.start R:34d8075638bd|xapi] start: making sure the VM really is halted [20120727T14:44:24.848Z|debug|vh10|1023 UNIX /var/lib/xcp/xapi|VM.start R:34d8075638bd|xapi] start: checking that VM can run on...