search for: dettaching

Does the "managed" attribute of the hostdev element for a USB device make a difference? The Domain XML Format docs has the following sentence for the hostdev element: If managed is omitted or "no", and for USB devices, the user is responsible to call virNodeDeviceDettach (or virsh nodedev-dettach) before starting the guest or hot-plugging the device, and virNodeDeviceReAttach

Hi! I am resending the following message about problems with utmp handling. * In the meantime I had some request in private mail from people asking whether I have new information. * The problem is still persistant in 2.9p2. * My own new investigations show, that the problem only appears with protocol 2, not with protocol 1, I therefore only started to note it when protocol 2 became the

Hi, my system (solaris b77) was physically destroyed and i loosed data saved in a zpool mirror. The only thing left is a dettached vdev from the pool. I''m aware that uberblock is gone and that i can''t import the pool. But i still hope their is a way or a tool (like tct http://www.porcupine.org/forensics/) i can go too recover at least partially some data) thanks in advance for

...1: channel 0: output drain -> closed debug1: channel 0: close_write debug1: channel 0: send close debug1: channel 0: is dead debug1: channel_free: channel 0: status: The following connections are open: #0 client-session (t4 r0 i8/0 o128/0 fd -1/-1) debug1: channel_free: channel 0: dettaching channel user debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 0.6 seconds debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0 debug1: Exit status 0 Wrong: debug1: Sending command: cat 1kfile debug1: channel 0: open confirm rwindow 0 rmax 16384 debug1: channel 0: read&...

...empty debug1: channel 0: output drain -> closed debug1: channel 0: close_write debug1: channel 0: send close debug1: channel 0: is dead debug1: channel_free: channel 0: status: The following connections are open: #0 client-session (t4 r0 i8/0 o128/0 fd -1/-1) debug1: channel_free: channel 0: dettaching channel user debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 0.1 seconds debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0 debug1: Exit status 0 Failure: OpenSSH_2.9p1, SSH protocols 1.5/2.0, OpenSSL 0x0090581f debug1: Reading configuration data /etc/ssh/ssh_config debug1: A...

...empty debug1: channel 0: output drain -> closed debug1: channel 0: close_write debug1: channel 0: send close debug1: channel 0: is dead debug1: channel_free: channel 0: status: The following connections are open: #0 client-session (t4 r0 i8/0 o128/0 fd -1/-1) debug1: channel_free: channel 0: dettaching channel user debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 0.2 seconds debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0 debug1: Exit status -1 (ssh2, no -n flag, exit status is 0) 3:32pm.orangecrush: ~> ssh -v qacrmdb /bin/true OpenSSH_2.9p1, SSH protocols 1.5/2.0, Ope...

I'm setting up a mail server in an active/passive cluster. Does any know of a guide that details how to setup 2 linux servers connecting to the same data array? I'm planning on using heartbeat but I do not see any array configuration in the documentation. Thanks, Ed

Hello, I have been struggling as of late to successfully configure a pci passthrough using libvirt with kvm. Hoping someone can shed some light on the problem. Overall my experience with virtualization limited is so please forgive. The guest runs fine till passthrough is configured. I am using virt-manager. This has been tried on both a Fedora17 x86_64 and Arch Linux x86_64 build with pretty much

...close debug1: channel 0: input open->closed debug1: channel 0: close_read debug1: channel 0: send close debug1: channel 0: full closed2 debug1: channel_free: channel 0: status: The following connections are open: #0 client-session (t4 r0 i8/0 o128/0 fd -1/-1) debug1: channel_free: channel 0: dettaching channel user debug2: !channel_still_open. debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 14.5 seconds debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0 debug1: Exit status -1 rsync error: unexplained error (code 255) at main.c(925) _exit_cleanup(code=255, file=main.c, line=925)...

...empty debug1: channel 0: output drain -> closed debug1: channel 0: close_write debug1: channel 0: send close debug1: channel 0: is dead debug1: channel_free: channel 0: status: The following connections are open: #0 client-session (t4 r0 i8/0 o128/0 fd -1/-1) debug1: channel_free: channel 0: dettaching channel user debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 0.2 seconds debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0 debug1: Exit status 0 bash-2.02$ ____________________________________________________________ Do You Yahoo!? Send a newsletter, share photos & files,...

The command "ssh ls -l /doesnotexist" gives various responses: Running from a 200 MHz PentiumPro with dsa key added to ssh-agent: Mistakes worst to fast machine: To a faster 600 MHz dual processor i686 600 MHz machine: ls: /doesnotexist: No such file or directory -- correct nothing at all -- wrong ls: select: Bad file descriptor -- wrong

...f empty debug1: channel 0: output drain -> closed debug1: channel 0: close_write debug1: channel 0: send close debug1: channel 0: is dead debug1: channel_free: channel 0: status: The following connections are open: #0 client-session (t4 r0 i8/0 o128/0 fd -1/-1) debug1: channel_free: channel 0: dettaching channel user debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 15.3 seconds debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0 debug1: Exit status -1 This is the debug when it works: OpenSSH_2.9p2, SSH protocols 1.5/2.0, OpenSSL 0x0090602f debug1: Reading configuration data /opt...

...pty debug1: channel 0: output drain -> closed debug1: channel 0: close_write debug1: channel 0: send close debug1: channel 0: full closed2 debug1: channel_free: channel 0: status: The following connections are open: #0 server-session (t4 r0 i8/0 o128/0 fd 7/7) debug1: channel_free: channel 0: dettaching channel user debug1: session_by_channel: session 0 channel 0 debug1: session_close_by_channel: channel 0 kill 6864 debug1: Received SIGCHLD. debug1: tvp!=NULL kid 1 mili 100 error: select: Bad file descriptor debug1: session_by_pid: pid 6864 debug1: session_free: session 0 pid 6864 debug1: !channel...

...ain -> closed debug1: channel 0: close_write debug1: channel 0: send close debug1: channel 0: is dead debug1: channel_free: channel 0: status: The following connections are open: #0 client-session (t4 r0 i8/0 o128/0 fd -1/-1) #1 x11 (t4 r3 i1/0 o32/0 fd 7/7) debug1: channel_free: channel 0: dettaching channel user debug1: channel 1: obuf empty debug1: channel 1: output drain -> closed debug1: channel 1: close_write debug1: channel 1: read<=0 rfd 7 len 0 debug1: channel 1: read failed debug1: channel 1: input open -> drain debug1: channel 1: close_read debug1: channel 1: input: no drain...

Hi, I cannot figure out how to draw a certain plot: could someone help me out? I have this data.frame from a survey my.data that looks like something like this: col1 col2 col3 col4 1 5 5 4 5 2 3 5 3 1 3 2 3 4 5 4 3 1 1 2 5 5 5 4 5 6 4 2 5 5 .... Each row represents a single questionnaire

...dead debug1: channel_free: channel 0: server-session, nchannels 4 - Client: debug1: channel_free: channel 0: status: The following connections are open: #0 client-session (t4 r0 i8/0 o128/0 fd -1/-1) #1 authentication agent connection (t4 r3 i1/0 o128/0 fd 7/7) debug1: channel_free: channel 0: dettaching channel user ^CKilled by signal 2. debug1: Calling cleanup 0x4000f70a(0x0) debug1: Calling cleanup 0x4000f892(0x0) Only when the client is shutdown with ^C, the connection will be closed as seen. Server: Connection closed by remote host. debug1: channel_free: channel 1: X11 inet listener, nchannel...

On Wed, May 23, 2001 at 10:49:54PM -0400, mugz wrote: > > I'm always a bit slow to report bugs i see, figuing someone else will > report it and that it will eventually get fixed. This one has been > somewhat of a problem for a while now. I run Linux Slackware -current and > just upgraded to OpenSSH 2.9p1, but I have noticed this same bug on every > platform and OS running

Hi list. I''m running Xen 4.0.1 on Debian. I''m trying to live resize a block device : - I have a arbitrary block device in my dom0 (/dev/mapper/vm-vol42). - I start a PV domain with that device as a disk (disk = [''phy:/dev/mapper/vm-vol42,xvda,w'']). - I resize vm-vol42 in the dom0 (adding size only) - the dom0 sees the device''s new size. -

The marilith boxes use a conserver (http://www.conserver.com/) setup for serial access. Our installation exports the logs via http allowing us to grab them with wget. Sending debug keys with is handled separately via xenuse. xenuse ultimately speaks to the conserver too but it abstracts away the IP and port to use so this is preferred. With these changes the correct Serial hostprop for a