search for: completed

Hello everybody, we recently got three Dell PowerEdge servers equipped with Qlogic QLE2462 cards (dual FC 4Gbps ports) and an EMC CLARiiON CX3-40 SAN. The servers with the FC cards were successfully and extensively tested with an older SUN StorEdge T3 SAN. However, when we connect them to the CX3-40, create and mount a new partition and then do something as simple as "tar -C /san -xf

Hi, I have a pretty simple problem. Here is the code: dat1=complete(dat.mice,1) dat2=complete(dat.mice,2) dat3=complete(dat.mice,3) dat4=complete(dat.mice,4) dat5=complete(dat.mice,5) dat6=complete(dat.mice,6) dat7=complete(dat.mice,7) dat8=complete(dat.mice,8) dat9=complete(dat.mice,9) dat10=complete(dat.mice,10) dat11=complete(dat.mice,11) dat12=complete(dat.mice,12)

Hello there, while bash completion was working great to me in CentOS6, since I'm using C7 I spend my day stuck on completion not working the way it should. The bad situations I'm facing are: - it doesn't expand *foo whereas there are *foo-named files in current dir, for instance: # rm *foo will show nothing whereas there's a file barfoo in curdir. - completion takes 10

> Date: Tue, 3 Feb 2015 09:36:01 -0800 > Subject: make install ignoring PREFIX for bash_completion > > I am trying to install the libguestfs python bindings in my > virtualenv. Since this cannot be done through PIP, The PIP problem is https://bugzilla.redhat.com/show_bug.cgi?id=1075594 Unfortunately we are stuck here because the pypi website still has a license that we cannot live

...;" "*" 18 LSUB "" "#shared/*" 19 LIST "" "#shared/doveimap/folder/subfolder" 20 SUBSCRIBE "#shared/doveimap/folder/subfolder" out : * NAMESPACE (("" "/")) (("#shared/" "/")) NIL 4 OK Namespace completed. * LIST (\Noselect) "/" "" 5 OK List completed. 6 OK Lsub completed. * LIST (\HasNoChildren) "/" "Trash" * LIST (\HasNoChildren) "/" "INBOX" * LIST (\Noselect \HasChildren) "/" "#shared" 7 OK List completed. 8 OK Lsub c...

I am trying to install the libguestfs python bindings in my virtualenv. Since this cannot be done through PIP, I was trying to do the following: https://github.com/libguestfs/libguestfs/commit/fcbfc4775fa2a44020974073594a745ca420d614 To get to building the python dist, I did the following: git clone https://github.com/libguestfs/libguestfs.git git checkout 1.28.5 ./autogen.sh --disable-php

Hello, I've just been hit by this old bug which is still present in 4.14: https://bugs.freedesktop.org/show_bug.cgi?id=80675 On MCP79 (ION), when stolen memory is set to 32MB in BIOS, console is blank but X11 works. When the stolen memory is increased to 64MB, console works fine. Bisected it to this: 4f6029da58ba9204c98e33f4f3737fe085c87a6f is the first bad commit commit

...In this case we have -specified a null completion callback. +specified a null completion callback. If a completion callback is +specified, it will only be called if the asynchronous command was +sucessfully submitted (if the asynchronous API itself returns an +error, there is nothing further to be completed). =back @@ -897,19 +904,25 @@ asynchronous commands are retired. =head2 Callbacks and locking -The callbacks are invoked at a point where the libnbd lock is held; as -such, it is unsafe for the callback to call any C<nbd_*> APIs on the -same nbd object, as it would cause deadlock. +The...

Hi everyone, I'm trying to get wine to work with CS3, but I can't seem to get it to work. I've tried copying some dll's, but it didn't help. I've reverted back to a clean install of Wine 1.0 now, and I was wondering if anyone could help? Code: fixme:ntdll:NtLockFile I/O completion on lock not implemented yet fixme:advapi:SetNamedSecurityInfoW L"C:\\Program

>> I am trying to install the libguestfs python bindings in my >> virtualenv. Since this cannot be done through PIP, > > The PIP problem is https://bugzilla.redhat.com/show_bug.cgi?id=1075594 > Unfortunately we are stuck here because the pypi website still has a > license that we cannot live with (it would have the effect of > assigning all work we upload to them). They

...own nouveau 0000:02:00.0: i2c: bus 0002: probing monitoring devices @@ -103,11 +103,11 @@ nouveau 0000:02:00.0: clk: 1b: 450000 KHz nouveau 0000:02:00.0: clk: --: core 450 MHz shader 1100 MHz vdec 450 MHz nouveau: DRM:00000000:00000080: init children... -nouveau: DRM:00000000:00000080: init completed in 71380us -[TTM] Zone kernel: Available graphics memory: 444902 kiB -[TTM] Zone highmem: Available graphics memory: 497930 kiB +nouveau: DRM:00000000:00000080: init completed in 71260us +[TTM] Zone kernel: Available graphics memory: 445198 kiB +[TTM] Zone highmem: Available graphics memory: 4818...

We have a memory leak when a function with a closure exits early prior to registering that closure through some path that will guarantee cleanup. The easiest way to fix it is to guarantee that once a closure is passed into a public API, it will be cleaned regardless of whether that API succeeds or fails. But to avoid cleaning the closure more than once, we need to refactor our internal handling,

I need some clarification on the FOID handed to zil_commit. I wrote a dscript to watch entry and return of zil_commit_writer. Here is an example output: <pre> 2009 Jan 23 23:34:36: ZIL Commit : Seq 183211310 : FOID 129644 Completed in 0 ms 2009 Jan 23 23:34:36: ZIL Commit : Seq 183211324 : FOID 129644 Completed in 0 ms 2009 Jan 23 23:34:36: ZIL Commit : Seq 183211386 : FOID 129644 Completed in 0 ms 2009 Jan 23 23:34:36: ZIL Commit : Seq 183211388 : FOID 129644 Completed in 0 ms 2009 Jan 23 23:34:...

I just purchased an Amfeltec USB-FXO adapter and am trying to compile DAHDI 2.10 on a Raspberry PI running Pidora 2014 R3. I have all the dependencies but I get an error and cannot finish. Is it even possible to compile DAHDI for the ARM plataform? Here is the error I am getting: root at astpi dahdi-linux-complete-2.10.2+2.10.2]# make make -C linux all make[1]: Entering directory

Errors follow: make make -C linux all make[1]: Entering directory `/usr/local/src/asterisk/dahdi-linux-complete-2.4.1.2+2.4.1/linux' make -C drivers/dahdi/firmware firmware-loaders make[2]: Entering directory `/usr/local/src/asterisk/dahdi-linux-complete-2.4.1.2+2.4.1/linux/drivers/dahdi/firmware' make[2]: Leaving directory

In general, autotooled packages are supposed to allow './configure --prefix=$HOME/subdir' as a way to then get 'make install' to run as non-root. In fact, 'make distcheck' tests that this scenario works; alas, we fail due to: /usr/bin/install -c -m 644 ../../../bash/nbdkit '/usr/share/bash-completion/completions' /usr/bin/install: cannot remove

...If a completion callback is > +specified, it will only be called if the asynchronous command was > +sucessfully submitted (if the asynchronous API itself returns an Should probably be "successfully" instead of "sucessfully". > +error, there is nothing further to be completed). > > =back > > @@ -897,19 +904,25 @@ asynchronous commands are retired. > > =head2 Callbacks and locking > > -The callbacks are invoked at a point where the libnbd lock is held; as > -such, it is unsafe for the callback to call any C<nbd_*> APIs on the > -sa...

Hi lld developers, As a GSoC student I wrote static ld.lld auto-completion scripts for zsh and bash shell because it doesn't have much options and flags for dynamic completion. Whether I send pr to zsh-completion/bash-completion package or open phabricator review for them? Also gnu ld has already autocompletion for bash shell but l am not merging ld and lld completion scripts to one file

...nch of conscriptors twice - how would you do > > deal with a big buffer that cointains a large number of small packets > > with respect to completions? > > - is one bit for completion enough? right now it means descriptor was > > actually used. how to we signal when it was completed? > > I am not sure I understand the difference. Under virtio, driver makes a > descriptor available, then device reads/writes memory depending on descriptor > type, then marks it as used. > > What does completed mean? > During the BOF, someone raised the point that there is...

...nch of conscriptors twice - how would you do > > deal with a big buffer that cointains a large number of small packets > > with respect to completions? > > - is one bit for completion enough? right now it means descriptor was > > actually used. how to we signal when it was completed? > > I am not sure I understand the difference. Under virtio, driver makes a > descriptor available, then device reads/writes memory depending on descriptor > type, then marks it as used. > > What does completed mean? > During the BOF, someone raised the point that there is...