search for: faffing

I hope this is the right place to post this. Apologies if not. My samba 3.0.4-3 install was working fine last night on debian 2.4.23 unstable (see uname below) and happily tranferring large files at 77 Mbps across my LAN (a first! but that's another story) until, suddenly, it stopped and would only move data at about .05 Mbps. Investigation was futile, so I uninstalled Samba and then

This bug is reported only on the VM's with CentOS 7 running on on VMware ESXi 5.1. The vSphere performance graph shows high CPU consume and disk activity only on VM's with CentOS 7. Sometimes I can not connect remotely with ssh (timeout error). The details of last issues was reported to retrace.fedoraproject.org. ?Do you have a hint? [root at vmguest ~]# abrt-cli list id

...ced that whilst I had upgraded to Xen 3.1 (kernel 2.6.18-xen), I''d forgot to upgrade the paravirt DomU .cfg kernels from 2.6.16-xen to reflect this. So, I upgraded the DomU kernels & ran into issues with mounting devices, and the ext3 module not being available. After a bit of faffing about, I managed to sort this out and load the ext3 module. However, now, in the domU''s dmesg, I see... --- ide_generic: no version for "struct_module" found: kernel tainted. --- Is this anything to be concerned about? How can I fix this? Running RHEL 4.5 Dom0, with CentOS 4...

On 04/12/2018 05:24 AM, Richard W.M. Jones wrote: > I don't think we have nbd-server in RHEL, and in any case wouldn't it > be better to use qemu-nbd? > > You just start a new qemu-nbd process instead of faffing around with > configuration files, kill the qemu-nbd process when you're done, and > qemu-nbd supports qcow2 already. That, and qemu-nbd supports extensions such as NBD_CMD_BLOCK_STATUS and NBD_OPT_STRUCTURED_REPLY that nbd-server has not implemented yet; a qemu NBD client talking to a q...

I have a pair of Asterisk servers which are happily routeing VoIP calls. I want to hook one of them to the PSTN. Given that I am in the UK, what is a reasonably easily-available device to provide an FXO interface from a Linux box, with a minimum of faffing around with drivers? Just one line is needed, though in theory two might eventually be useful. My usual white-box hardware suppliers don't seem to play in this field. Also: I've heard good things about the PAP2T for getting analogue handsets to talk to a VoIP server. But all the ones I can...

I am trying to install wine-20050211 on my second system, which runs SuSE 9.2. After much faffing around I finally managed to download and install bison, which allowed ./config to complete. A warning at the end advised me to install xlib-devel or xfree86-devel. Googling around I found the RPM for XFree86-devel for SuSE 9.1 so I downloaded it and started to install it. Unfortunately, a mi...

...th SIP (I think they might only come in SIP flavour actually?). I am quite excited about the possibilities with this kit - especially video calls. Unlike the earlier Cisco phones (e.g. 79 series), these can't be used standalone, and require a TFTP server to get their config. After many hours of faffing, I've got the basic config parsing OK, but now I am stuck. The phone won't actually finish booting without access to a couple more files - a g4_tones.xml (which I've created from a g3_tones I found kicking about, following a tip on the net) and gd_sip.jar which seems to contain locale s...

On Thu, Apr 12, 2018 at 2:07 AM Nir Soffer <nirsof@gmail.com> wrote: > On Tue, Apr 10, 2018 at 6:53 PM Richard W.M. Jones <rjones@redhat.com> > wrote: > ... > Dan Berrange pointed out earlier on that it might be easier if imageio >> > just exposed NBD, or if we found a way to tunnel NBD requests over web >> sockets (in the format case nbdkit would not be

...variable is the severity of diseases, going from 0 to 5 (the severity is actually an ordered factor). The independent variables are: 1 genetic marker, time of medical observation, age, sex. What I *need* is a p-value for the genetic marker. Because I have ~1.5 million markers I'd rather not faffing around too much. My model is: > mod.vglm = vglm(disease.status ~ x + time + age + sex, family = cumulative(par = T)) where x is my genetic marker, coded as 0/1/2, time is days of medical observation. > summary(mod.vglm) works: Call: vglm(formula = disease.status ~ x + time + age + sex...

https://bugs.freedesktop.org/show_bug.cgi?id=94727 Bug ID: 94727 Summary: nouveau/pushbuf.c:238: pushbuf_krel: Assertion `bkref` failed. Product: Mesa Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

...for adding export dynamically: > https://github.com/NetworkBlockDevice/nbd/blob/cb6e816c4d2c536cfff5ba9859f210aabe39539b/nbd-server.c#L3007 I don't think we have nbd-server in RHEL, and in any case wouldn't it be better to use qemu-nbd? You just start a new qemu-nbd process instead of faffing around with configuration files, kill the qemu-nbd process when you're done, and qemu-nbd supports qcow2 already. It doesn't support progress, but it's not very clear what "progress" means for an NBD connection, since it's quite reasonable to go back and rewrite blocks, o...

...Eric Blake <eblake@redhat.com> wrote: > On 04/12/2018 05:24 AM, Richard W.M. Jones wrote: > > > I don't think we have nbd-server in RHEL, and in any case wouldn't it > > be better to use qemu-nbd? > > > > You just start a new qemu-nbd process instead of faffing around with > > configuration files, kill the qemu-nbd process when you're done, and > qemu-nbd supports qcow2 already. > That, and qemu-nbd supports extensions such as NBD_CMD_BLOCK_STATUS and > NBD_OPT_STRUCTURED_REPLY that nbd-server has not implemented yet; a qemu > NBD...

there is this plugin to use APNS to notify phones, its a faf though as you need a legal OSX Server to generate the signing keys, I never ended up implementing it. https://github.com/st3fan/dovecot-xaps-daemon Aki Tuomi wrote on 29/03/2017 07:29: > > On 29.03.2017 07:24, mca at caloro.ch wrote: >> Hello >> >> >> >> Please exist in Dovecot 2.2.13 the

Hi Everyone, After a fair amount of faffing ive managed to get the 2000w working with asterisk for IP -> PSTN calls (i.e. get the phone to make and receive calls over our BT line). The final solution is to set up outgoing VoIP calls but I now know that without a SIP aware router I can think again! (damn you iptables!) In the mean time I...

----- Original Message ----- > Roger Burton West wrote: > > > I want to hook one of them to the PSTN. Given that I am in > > the UK, what is a reasonably easily-available device to > > provide an FXO interface from a Linux box, with a minimum of > > faffing around with drivers? Just one line is needed, though > > in theory two might eventually be useful. My usual white-box > > hardware suppliers don't seem to play in this field. > > I've had good experiences with an OpenVox A400P, once you've done the > "Dahdi &g...

...ship between LVM objects, by which I mean "what PVs contain a VG?", or "what LVs are contained in a VG?" This simple API exposes that to callers. {lv,vg,pv}uuid: Return the UUID of an LVM object. You can already get this using (eg.) lvs_full, but this is a lot less faffing around. vg{lv,pv}uuids: Return the LVs belonging to a VG, or the PVs containing a VG. It returns them as UUIDs, so if you build up a map using the previous calls, then you can map them back to names, or keep them as UUIDs as required. There's an example Perl program includ...

ABRT is a collection of scripts that makes it easier to report bugs and crashes in various components of the distribution to a central server. Metadata from this allows developers and upstream projects to evaluate their priority chain, and also get crucial information on why their software might not be performing as expected on CentOS Linux. This information is sent to the server in a json format

Hi, folks, I'm installing a RAID controller card for a large external RAID box in a Dell server. I've got two riser slots available. Here's the question: the controller card has some large chips on one side, and if I put it in riser 1, those chips face downwards in the box, blocking ease of cooling, while if I put it in riser 2, the chips will face up... but be right over a large

On 03/08/2017 07:39 AM, John Hodrien wrote: > On Wed, 8 Mar 2017, Steve Clark wrote: > >> Yes it is really hard! >> >> ip address add 192.168.0.1/24 dev enp0s25 >> ip route add default via 192.168.0.254 dev enp0s25 >> echo nameserver 8.8.8.8 > /etc/resolv.conf >> echo nameserver 8.8.4.4 >> /etc/resolv.conf > This is still a deliberately trivial