search for: invetigate

Displaying 5 results from an estimated 5 matches for "invetigate".

Did you mean: investigate
2006 Nov 08
2
Sweave and font problems
Dear All, Having now successfully started using Sweave, I have just noticed an odd side effect with fonts. Using plain LaTeX, I have had no problems using \usepackage{palatino} or \usepackage{times} and the font correctly changes. However, once I convert the tex document into Snw, and run it through R CMD SWEAVE, LaTeX seems to ignore this package directive. The LaTeX log suggests the font
2004 Jul 28
2
Asterisk voicemail from mysql no longer working
Hi All, I hope someone can help. I have a system that I have recently upgraded to latest CVS and my voicemail is not working from mysql database. I get an error on the console saying " No entry in voicemail config file for 'number'" whilst there is an entry in the database for the specified number. It seems like app_voicemail is no longer checking the database even though
2014 Jul 15
2
Re: virt-resize: support to MBR logical partitions and some question
...could be: 1. as the error message suggests, rebooting. But I don't known how since it runs in an applicance if I'm right. 2. fix parted informing the kernel about modifications to partitions. Do you have any insight of this? If you think this is a possible solution I'll start invetigate it. Regards, Hu
2014 Jun 04
3
virt-resize: support to MBR logical partitions and some question
Hi, I'm adding support to resizing logical partitions(patch is in progess). But encounter an error when adding a logical partition in dest image: virt-resize: libguestfs error: part_add: parted: /dev/sdb: Warning: The resulting partition is not properly aligned for best performance. Error: Error informing the kernel about modifications to partition /dev/sdb5 -- Device or resource busy.
2005 Aug 12
5
Functions that return objects...
I was investigating why the find dialog causes an error when you close it. It seems that wxRuby2 is returning a new ruby object when you call Event.get_dialog. This causes some big problems when you''re expecting you''re going to get back the same ruby pointer that you put in. In a brief check over the source I don''t see anything that preserves the original ruby