search for: relect

I''m seeing these in my logs on my puppetmaster: puppetmasterd[4111]: Could not store configs: SQLite3::SQLException: SQL logic error or missing database: DELETE FROM fact_values WHERE "id" = 8 currently this is 0.24.0 relect from some previously collected resource that wasn''t cleaned up? upgrade issue? nothing to worry about? that''s the only message I''m getting and storeconfigs seem to be working otherwise. -- stickm@gmail.com -==< Stick >==- ______________________________________...

...s to. User B, normal user, can't connect, gets denied right off the bat at the login screen, password has been verified. The admin has verified the configuration and it looks good. Now User C, me, has been brought in. We duplicated user A, and just changed the names to warp the innocent and relect me, not her. I hop on my NT-4 laptop and open the shares. I can see "\\machine" just fine, but when I click to open the directories in question, I put in my info and am denied. One odditiy, I pumped up the debug to 3 and restarted. Then I tried to connect again. I get 3 invalid use...

...socket path because it's a host > + * filesystem name. The client might not really be running on the > + * same machine (eg. it using a proxy). However it doesn't even missing 'is' > +++ b/tests/test-reflection-address.sh > @@ -0,0 +1,63 @@ > +# Test the relection plugin with mode=address. reflection (hmm, I missed that typo in patch 1, where this was copied from) > +# Run nbdkit. > +start_nbdkit -P reflection-address.pid -U $sock \ > + reflection mode=address Is it worth also trying to test a TCP socket (although we have to worry about...

I have a extension 981 setup for entering VoiceMailMain: exten => 981,1,VoiceMailMain,([mailbox]@usvm) exten => 981,2,HangUp() I want to pass the calling extension to the context (extension and mailbox numbers are the same). This dosen't seem to work. I get this in the console: Asterisk Ready. *CLI> -- Executing VoiceMailMain("SIP/2504-ba66",

...* filesystem name. The client might not really be running on the > > + * same machine (eg. it using a proxy). However it doesn't even > > missing 'is' Will fix. > > +++ b/tests/test-reflection-address.sh > > @@ -0,0 +1,63 @@ > > > +# Test the relection plugin with mode=address. > > reflection (hmm, I missed that typo in patch 1, where this was copied from) Oops - fixed in all 3 places. > > +# Run nbdkit. > > +start_nbdkit -P reflection-address.pid -U $sock \ > > + reflection mode=address > > Is it worth...

...A, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND +# ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, +# OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT +# OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +# SUCH DAMAGE. + +# Test the relection plugin with base64-encoded export name. + +source ./functions.sh +set -e +set -x + +requires nbdsh --version +# XXX This needs to test $PYTHON somehow. +#requires python -c 'import base64' + +# Test if mode=base64exportname is supported in this build. +if ! nbdkit reflection --dump-plugi...

...A, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND +# ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, +# OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT +# OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +# SUCH DAMAGE. + +# Test the relection plugin with mode=address. + +source ./functions.sh +set -e +set -x + +requires nbdsh --version + +sock=`mktemp -u` +files="reflection-address.out reflection-address.pid $sock" +rm -f $files +cleanup_fn rm -f $files + +# Run nbdkit. +start_nbdkit -P reflection-address.pid -U $sock \ +...

This series is based on my blog posting here: https://rwmj.wordpress.com/2019/09/13/nbdkit-supports-exportnames/ It depends on the fix for realloc: https://www.redhat.com/archives/libguestfs/2019-September/thread.html#00103 This series adds a fun plugin, and also an semi-related feature I've long thought to be desirable. You can consider patches 1 & 4, and patches 2 & 3 as forming

...and is not close to anywhere other than itself :-). This version adds considerable functionality and (we hope) stability to R. Most notably, the object system is now very close to that of S and we now have a fairly full implementation of complex arithmetic. The jump in version number (from 0.16) relects the fact that we feel that this version of R represents quite a jump toward what we hope will be in our eventual 1.0 release. However the version is numbered 0.49 rather than the 0.50 we touted because it falls a little short of what we really want for 0.50. Immediate development of R will focus...

...and is not close to anywhere other than itself :-). This version adds considerable functionality and (we hope) stability to R. Most notably, the object system is now very close to that of S and we now have a fairly full implementation of complex arithmetic. The jump in version number (from 0.16) relects the fact that we feel that this version of R represents quite a jump toward what we hope will be in our eventual 1.0 release. However the version is numbered 0.49 rather than the 0.50 we touted because it falls a little short of what we really want for 0.50. Immediate development of R will focus...

...and is not close to anywhere other than itself :-). This version adds considerable functionality and (we hope) stability to R. Most notably, the object system is now very close to that of S and we now have a fairly full implementation of complex arithmetic. The jump in version number (from 0.16) relects the fact that we feel that this version of R represents quite a jump toward what we hope will be in our eventual 1.0 release. However the version is numbered 0.49 rather than the 0.50 we touted because it falls a little short of what we really want for 0.50. Immediate development of R will focus...