search for: fuddl

...I stopped. My issues are: 1. XenServer mounts the NFS servers SR subdirectory, not the export. Gluster won't do that. -- I can, apparently, mount the gluster export somewhere else, and then 'mount --bind' the subdir to the right place 2. I don't really know python, though I could fuddle my way through it, I guess. What I thought would be cool, was to modify the nfs.py mount script. If the 'Advanced Options' field contained the word gluster, then instead of an NFS mount happening, it would do the gluster mount. All the magic of the NFS mount would remain, and happen on th...

...don't work with mbox, so in my mind, how do you avoid corruption and why not just make a normal account and let people hack away at the data? I've not even got to the questions in my mind about how to set up the account, but figured if I could get the above straight, I might be able to fuddle my way through it. Help would be truly appreciated. steve campbell

...easily. Problem is, I can't figure out how to store the results. Each result is a vector of widely varying lengths. Ideally I'd like a vector of these, i.e. a vector of vectors, so I can quickly iterate through them and compute correlation coefficients. Here's a transcript of my fuddling to date: > x <- c(1,2,3) > y <- c(4,5) > v <- list("1"=x, "2"=y) > unlist(v["1"]) 11 12 13 1 2 3 > unlist(v["1"])[1] 11 1 > unlist(v["1"])[2] 12 2 > unlist(v["1"])[3] 13 3 > unlist(v[&...

Hi Users NUT, I want monitor a UPS of brand SMS (Sinus Double 8 KVA) using a raspberry-pi. In compatibility list, is listed to use the blazer_ser driver. I use a USB adapter to RS-232 conected in to the No-Breake. Follow the comands e confs. root at rasp:/home/pi# lsusb *Bus 001 Device 004: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port* Bus 001 Device 003: ID 0424:ec00 Standard

...uestions: 1. Are you sure that /dev/ttyUSB0 exists and is the result of the Prolific USB->serial converter? For example, if you yank the Prolific and reboot, is /ttyUSB0 there still? It is possible that there is another /dev/ttyUSBx out there.I doubt this but wonder. 2. I have recently been fuddled due to permission problems of various sorts. Are you sure that the user under which nut is running is able to access the /dev/ttyUSB file? On 8/6/2019 6:14 AM, Mario Michielin Neto wrote: > Hi Users NUT, > > I want monitor a UPS of brand SMS (Sinus Double 8 KVA) using a > raspberr...

...ls. When only one call is passed through an IAX trunk, the IP overhead is indecent. I would like to increase the IAX voice packet emission interval (20ms - i'm using speex) to something much larger, in order for the packets to transport as much data as possible. I've been trying to fuddle with the "trunkfreq" parameter and push it to 80ms, but that did not change the voice packet rate at all. How can I change that voice packet rate ? Thanks ! -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/as...

...roximity in the log. It would probably work for most of the instances, but it would not be 100% viable, meaning we would be getting compaints and questions from our user "I ain't got that share?! WTF!!" I was going to wait to hear from Jeremy Allison before I get serious about either fuddling about with the netapp smb.conf or parsing logs on the msdfs box. 'til then, Greg Enlow -- Greg Enlow grenlow at hk.mailbox.de On 21 May 2015, at 05:09, David Bear wrote: Well, this doesn't fix the preexec issue, but you might scan through the samba logs finding connections to the...

The user has the option of disabling the platform driver: 00:02.0 Unassigned class [ff80]: XenSource, Inc. Xen Platform Device (rev 01) which is used to unplug the emulated drivers (IDE, Realtek 8169, etc) and allow the PV drivers to take over. If the user wishes to disable that they can set: xen_platform_pci=0 (in the guest config file) or xen_emul_unplug=never (on the Linux command

Hi, Thank you for you input! We tried that already. That, however, doesn't do the same thing. It is then simply a DFS server and not the "magical" msdfs proxy - yes the user can now click on a link to get to the desired spot, but the proxy function _automagically_ sends the user, when they access the msdfs share, to the netapp's readonly share without the extra click. And it