search for: alwayes

On Thu, Jun 26, 2014 at 3:39 PM, Robinson, Paul <Paul_Robinson at playstation.sony.com> wrote: > The main motivation for turning it off is that no known consumer (debugger) > took advantage of it. > > Turning it on does more than slightly increase the object file size, it can > cause the same source line to be listed multiple times in the .debug_line > table (with different

Hello, I'm running FreeBSD 9.0/amd64, pure ZFS setup, one Seagate disk ST2000NM0011 SN02 on LSI Logic (mpt) controller. Yes, I know that running one disk on RAID controller is a bit weird, I have to find yet if it is possible to connect disk to internal SATA controller. About two days ago, system became SLOW. Disk usage is constantly 100%, and sometimes I'm getting swap_pager:

Two days ago I installed a brand new SSDNow E50 series (Enterprise) disk on a server. I intend to move the OS there. I just did the physical install and copied a few files to and from it just to see if it was OK. I left it there, waiting for an opportunity to configure it to do real work. Now I have looked at it with smartctl -a and it gives me the following info: 1 Raw_Read_Error_Rate

Always... Desire that in the New Year that if you really initiate... It hears the words that always it desired to hear. It pronounces the phrases that one day it desired to repeat. It feels the emotion that always waited to feel. It walks for the tracks that one day it desired to follow. It divides the affection with who always desired to distribute. It hugs all the friends whom always it desired

Asterisk is reporting the following error: [Apr 15 16:58:32] WARNING[14759] ast_expr2.fl: ast_yyerror(): syntax error: syntax error, unexpected ':', expecting $end; Input: : Always ^ here is the dialplan: exten => OUT,1,Gotoif($[$["${DB(AMPUSER/${ARG1}/recording)}" : "out=([^|]+)"] = Always]?r,1) exten =>

Hi, On Mon, 2016-10-24 at 12:07 +0200, Alessandro Baggi wrote: > === START OF READ SMART DATA SECTION === > SMART Error Log not supported I reckon there's a <snip> between those lines. The line right after the first should read something like: SMART overall-health self-assessment test result: PASSED or "FAILED" for that matter. If not try running smartctl -t short

It's not a big deal, but it always annoyed me a bit when I hit it, so I'll bring it up here. LLD represents an alignment X as log2(X) in some places and just X in other places. It's a bit confusing. Because I always think alignments in my mind in terms of 1, 2, 4, 8, ..., instead of 2^1, 2^2, 2^3, ..., I'd like to propose to always use real values. Any objections? --------------

After having massive problems with a supermicro X7DBE box using AOC-SAT2-MV8 Marvell controllers and opensolaris snv79 (same as described here: http://sunsolve.sun.com/search/document.do?assetkey=1-66-233341-1) we just start over using new hardware and opensolaris 2008.05 upgraded to snv94. We used again a supermicro X7DBE but now with two LSI SAS3081E SAS controllers. And guess what? Now we get

This involves some significant changes to this test framework. In particular: - Instead of just specifying $srcdir at the start of a FileIn path, you can now specify arbitrary environment variables. This is necessary to allow the tests to run from a tmpdir. - Use COPYING instead of COPYING.LIB, and copy that file into the test suite directory. - Require the static binaries

In a server with raid1 a first smart error was reported. Smart attributes: SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time

Hi. I found that DTX is always unavailable when DISABLE_FLAOT_API is not defined in OPUS_AUTO mode. As you know analysis_info.valid is alway true except NaN case and is_silence is alway true except digital zero signal case. In general, following condition will be alway true except exceptional case. (analysis_info.valid || is_silence) But in a code, there is a NOT expression in front of above

Modify "tests" to expand any kind of environment variable than just $srcdir; use $datadir and $databuilddir to point to the files in $srcdir/tests/data and $builddir/tests/data, so it is easier to point at the data for the tests. Most of the work (except the $databuilddir and the integration in the Makefile.am) has been done as part of larger changes by Richard W.M. Jones

With the Magical Jelly Bean Keyfinder running in Wine in Linux with Gnome/Metacity, the syncing of the "Always On Top Status" is one-way. Under tools, Keyfinder has an "Always On Top" option. If you put the window into "Always On Top" mode via the keyfinder's option under tools, when you right-click on the window bar, you will see that, according to

On Thu, 27 Oct 2016 11:25, Alessandro Baggi wrote: > Il 24/10/2016 14:05, Leonard den Ottolander ha scritto: >> On Mon, 2016-10-24 at 12:07 +0200, Alessandro Baggi wrote: >> > === START OF READ SMART DATA SECTION === >> > SMART Error Log not supported >> >> I reckon there's a <snip> between those lines. The line right after the >> first

This is a follow-up to the other generator changes in: https://www.redhat.com/archives/libguestfs/2017-February/msg00217.html Rich.

The previously library-side ‘file_architecture’ API is reimplemented in the daemon, in OCaml. There are some significant differences compared to the C implementation: - The C code used libmagic. That is replaced by calling the ‘file’ command (because that is simpler than using the library). - The C code had extra cases to deal with compressed files. This is not necessary since the

> -----Original Message----- > From: Jason Pyeron > Sent: Saturday, February 07, 2015 22:54 > > NOTE: this is happening on Centos 6 x86_64, > 2.6.32-504.3.3.el6.x86_64 not Centos 5 > > Dell PowerEdge 2970, Seagate SATA drive, non-raid. > > I have this server which has been dying randomly, with no logs. Here is a console picture. http://i.imgur.com/ZYHlB82.jpg

Il 24/10/2016 14:05, Leonard den Ottolander ha scritto: > Hi, > > On Mon, 2016-10-24 at 12:07 +0200, Alessandro Baggi wrote: >> === START OF READ SMART DATA SECTION === >> SMART Error Log not supported > > I reckon there's a <snip> between those lines. The line right after the > first should read something like: > > SMART overall-health self-assessment

I finally fixed my drive error problem. This has been going on quite a while. I've posted before with no success on getting this fixed. I was getting these errors. Dec 4 04:03:10 bikesn4x4s kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } Dec 4 04:03:10 bikesn4x4s kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC } And now for the amazing smartctl -a

Hi all. I have one server with problem in maillog: Feb 6 06:46:26 host1 postfix/qmgr[24296]: fatal: qmgr_move: update active/4DE015AC536 time stamps: Stale NFS file handle Feb 6 06:46:27 host1 postfix/master[4487]: warning: process /usr/libexec/postfix/qmgr pid 24296 exit status 1 Feb 6 06:46:27 host1 postfix/master[4487]: warning: /usr/libexec/postfix/qmgr: bad command startup -- throttling