search for: brining

Hi, sorry if I am brining up old news, but I couldn''t find a good answer searching the previous posts (My mom always says I am bad with finding things :) However I noticed a difference when creating a zfs filesystem compared with a vxfs filesystem in the available size. ie. ZFS zonedata/zfs [b]392G[/b] 12...

Curious if any one has looked at or done a trial of Novell''s PlateSpin Orchestrate? Just watched their webcast presentation on it and it looks interesting. Thanks, James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

...complex question that is not answered easily, so let me refine it some more. The type of scripts that I'm dealing with are well suited to parallelisation - often they involve mapping out parameter space by changing a single parameter and then re-running the simulation 10 (or n times), and then brining all the results back to gether at the end for analysis. If I can distribute the runs over all the processors available in my machine, I'm going to roughly halve the run speed. The question is, how to do this? I've looked at many of the packages in this area: rmpi, snow, snowFT, rpvm, and t...

On Mon, 2016-02-08 at 14:22 -0800, John R Pierce wrote: > the only truly safe way to destroy data on magnetic media is to grind > the media up into filings or melt it down in a furnace. I unscrew the casing, extract the disk platter(s), slide a very strong magnet over both sides of the platter surface then bend the platter in half. How secure is that ? I can't afford a machine that

> -----Original Message----- > From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On > Behalf Of EGO-II.1 > Sent: den 9 februari 2016 09:00 > To: CentOS mailing list > Subject: Re: [CentOS] Utility to zero unused blocks on disk > > > > >> the only truly safe way to destroy data on magnetic media is to grind > >> the media up into

I updated DwarfDebug to use section offset, instead of hard coding 0, to handle LTO properly. r107202. Thanks for brining this up. - Devang On Tue, Jun 29, 2010 at 11:27 AM, Devang Patel <devang.patel at gmail.com> wrote: > DW_AT_stmt_list attribute's value is a section offset to the line no > info for current compilation unit. If there is only one  compilation > unit generated per .o file then it...

...is is to reinforce the "there be > dragons here" nature of this feature. It interacts with other parts of the > assembler and the underlying assumptions of the platform in interesting > ways. Lots of *really* careful test cases will be necessary. Yes I see your point. Thanks for brining .subsections_via_symbols to my attention.

...o whether this will sort out the problem, but they replied with a very vague answer. Can somebody please shed some light on this : is this version of OCFS that we are running very buggy and causes lots of problems like this? And if we upgrade is it going to sort out the problem, or are we just brining ourselves into "Supported-land" and we can get fixed from there? Also(sorry for all the questions :), when we upgrade, is it just a case of upgrading the kernel and the OCFS rpm's? Thank you for your help in advance...much appreciated!! -- Mark Maiden Systems Administrator Globof...

Hi, this is my first post to this list, so please excuse if submitting a patch without previous discussion is considered bad form or anything similar. I encountered a bug in the CMake build while using MinGW (non-MSYS, non-CYGWIN) where the LTO_export fails with a "The syntax of the command is incorrect" error. This error was previously fixed for Windows in general using

..., flushing the user wouldn't have helped. The only remedy was to kill dovecot on every box in the director cluster and then (with dovecot down on *all* of them) start dovecot back up. Restarting each director's dovecot (with other directors' dovecots still running) did nothing. Only by brining the entire cluster down did dovecot stop furiously logging "Host ... is being updated before previous update had finished" on every director host. Any advice is most welcome.

On Nov 1, 2013, at 12:15 PM, David Peixotto <dpeixott at codeaurora.org> wrote: >>>>> I was thinking that without the .ltorg directive the constant pool >>>>> would go at the end of the section. >>>>> >>>> So where does the assembler place the constant pool(s) if that >>>> directive isn't present? I was under the

.... >> >> The only remedy was to kill dovecot on every box in the director cluster >> and then (with dovecot down on *all* of them) start dovecot back up. >> Restarting each director's dovecot (with other directors' dovecots still >> running) did nothing. Only by brining the entire cluster down did dovecot >> stop furiously logging "Host ... is being updated before previous update >> had finished" on every director host. >> >> Any advice is most welcome. >> > > > Dovecot guys, > > Any thing I can do to fix this...

DW_AT_stmt_list attribute's value is a section offset to the line no info for current compilation unit. If there is only one compilation unit generated per .o file then it is always zero. What kind of errors are you seeing ? - Devang On Tue, Jun 29, 2010 at 9:02 AM, Artur Pietrek <pietreka at gmail.com> wrote: > Hi all, > While implementing debug info for our backend, we've

On 02/08/2016 07:38 PM, Always Learning wrote: > On Mon, 2016-02-08 at 14:22 -0800, John R Pierce wrote: > >> the only truly safe way to destroy data on magnetic media is to grind >> the media up into filings or melt it down in a furnace. > I unscrew the casing, extract the disk platter(s), slide a very strong > magnet over both sides of the platter surface then bend the

If you adjust the my.cnf file to make separate instances of mysql..... How would you go through the mysql secure installation? Is is possible or must it all be done manually for each one? is it possible to make each one of those instances a replicate/slave of a different master (thus a backup mysql server in a way?) working on this now, but having issues getting it to work. (centos 6)

...otocol, which will be incompatible with the standing 0.3 protocol (version 4). Whether or not the next version will be able to speak with older versions is still unclear. Because tinc has gained in stability over the last few weeks, it seems reasonable to call this next version `1.0'. Before brining out the final 1.0, we'll distribute a few prereleases, so everybody gets a fair chance to experiment, and we have some time to squash any bugs left. Thanks to Lubom?r Bulej and Mads Kiilerich, there will be rpms of this version, and if everything goes well, there will also be a deb of it. Tha...

...other version is already loaded and behave accordingly (throw an error, do nothing if other version is more recent, override if other version is older). I''m sure this will help to prevent lot''s of situations where Prototype is loaded more than once by different libraries each one brining it''s own (and probably conflicting at some point) Prototype version. The situation is very similar when, say, different Java third-party libraries bring different versions of other libraries they depend on (like Log4j). Today Maven helps to solve it but it''s still a very well kno...

...constant, because it is the linker who knows the correct offset. Artur On Tue, Jun 29, 2010 at 10:18 PM, Devang Patel <devang.patel at gmail.com>wrote: > I updated DwarfDebug to use section offset, instead of hard coding 0, > to handle LTO properly. > r107202. > > Thanks for brining this up. > - > Devang > > On Tue, Jun 29, 2010 at 11:27 AM, Devang Patel <devang.patel at gmail.com> > wrote: > > DW_AT_stmt_list attribute's value is a section offset to the line no > > info for current compilation unit. If there is only one compilation > &...

Hi all, While implementing debug info for our backend, we've noticed a problem with debug_line section. We believe that the following code is wrong: // DW_AT_stmt_list is a offset of line number information for this // compile unit in debug_line section. It is always zero when only one // compile unit is emitted in one object file. addUInt(Die, dwarf::DW_AT_stmt_list, dwarf::DW_FORM_data4,

...dn't have helped. > > The only remedy was to kill dovecot on every box in the director cluster > and then (with dovecot down on *all* of them) start dovecot back up. > Restarting each director's dovecot (with other directors' dovecots still > running) did nothing. Only by brining the entire cluster down did dovecot > stop furiously logging "Host ... is being updated before previous update > had finished" on every director host. > > Any advice is most welcome. > Dovecot guys, Any thing I can do to fix this? Any thoughts on that error in general?