search for: larger

...21600.000 -> 20672.000: 1.0449x smaller > Usage over time: http://tinyurl.com/35rclpd > > ### float ### > Mem max: 15904.000 -> 15852.000: 1.0033x smaller > Usage over time: http://tinyurl.com/2vokmep > > ### hg_startup ### > Mem max: 7000.000 -> 7012.000: 1.0017x larger > Usage over time: http://tinyurl.com/3x4wneu > > ### iterative_count ### > Mem max: 9992.000 -> 9908.000: 1.0085x smaller > Usage over time: http://tinyurl.com/24dy7ql > > ### nbody ### > Mem max: 13552.000 -> 13240.000: 1.0236x smaller > Usage over time: http://...

...rl.com/2a62cbv ### django ### Mem max: 21600.000 -> 20672.000: 1.0449x smaller Usage over time: http://tinyurl.com/35rclpd ### float ### Mem max: 15904.000 -> 15852.000: 1.0033x smaller Usage over time: http://tinyurl.com/2vokmep ### hg_startup ### Mem max: 7000.000 -> 7012.000: 1.0017x larger Usage over time: http://tinyurl.com/3x4wneu ### iterative_count ### Mem max: 9992.000 -> 9908.000: 1.0085x smaller Usage over time: http://tinyurl.com/24dy7ql ### nbody ### Mem max: 13552.000 -> 13240.000: 1.0236x smaller Usage over time: http://tinyurl.com/23dstyu ### normal_startup ### M...

Hi all, running 6.5 on a HP DL380p with a few logical drive created with the onboard RAID.? I see these when the system boot.? How can I fix this? scsi: host 2 channel 0 id 0 lun4194304 has a LUN larger than allowed by the host adapter scsi: host 2 channel 0 id 0 lun4194560 has a LUN larger than allowed by the host adapter scsi: host 2 channel 0 id 0 lun4194816 has a LUN larger than allowed by the host adapter scsi: host 2 channel 0 id 0 lun4195072 has a LUN larger than allowed by the host adapter...

<p><span style="font-size: larger"><span style="font-family: Times New Roman">Hi "Zach--the blind bike rider", <br /> <br /> Your friend Timothy Clark registered for the FREE Spiritual Path to Money Telesummit today, & thought you might be interested too : <a href='http://www...

...gcGQ33LfzdT4h: from=<list at someml.tld>, size=12064, nrcpt=1 (queue active) Mar 20 22:17:02 gaia postfix/smtpd[18941]: disconnect from some.list.server[1.2.3.4] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7 Mar 20 22:17:02 gaia dovecot: lmtp(18954): Error: /proc/self/status is larger than expected Mar 20 22:17:02 gaia dovecot: lmtp(18954): Connect from local Mar 20 22:17:02 gaia dovecot: lmtp(sam at samresto.dev)<18954><vbRKLa4hGWQKSgAAw1YR2w>: Error: /proc/self/status is larger than expected Mar 20 22:17:02 gaia dovecot: message repeated 2 times: [ lmtp(sam at s...

I've been attempting to create a bootable image thats double the size of the 2880 floppy disk. I can do the following to create a image that will boot with memdisk but i cant seam to get it to work with a larger size. What works... dd if=/dev/zero of=floppy288.img bs=1024 count=2880 mkdosfs floppy288.img ms-sys -1 -f floppy288.img mount -o loop floppy288.img /mnt cp msdos.sys /mnt/ cp io.sys /mnt/ cp command.com /mnt/ I then boot that using PXE and it work...

...ies are numerical vectors. I would like to present this as a table (or something that looks like a table) but instead of the numbers I would like to present circles (pch = 19) that increases in size with increasing number. Is it also possible to make it change color if the value is negative. (E.g. larger blue circles represent larger +values while larger red circles represent larger -values)? Jonas -- View this message in context: http://r.789695.n4.nabble.com/table-with-values-as-dots-in-increasing-sizes-tp3028297p3028297.html Sent from the R help mailing list archive at Nabble.com.

Hi, all ecdf function (Empirical Cumulative Distribution Function) in "stats" package counts from smaller values to larger values. However, I want to draw it by counting from larger value to smaller values and I couldn't find options for this purpose. How can I draw ecdf or ecdf like graph by counting from larger values to smaller values. Thank you in advance. Hyunchul Kim [[alternative HTML version deleted]]

I have a 10x2 distributed replica volume running gluster3.8. Each of my bricks is about 60TB in size. ( 6TB drives Raid 6 10+2 ) I am running of storage so I intend on adding servers with larger 8Tb drives. My new bricks will be 80TB in size. I will make sure the replica to the larger brick will match in size. Will gluster place more files on the larger bricks? Or will I have wasted space? In other words will the 80TB new bricks ever exceed 60TB? -Mark -------------- next part ----------...

...43040 512-byte hdwr sectors (21475 MB) SCSI device sda: drive cache: write back SCSI device sda: 41943040 512-byte hdwr sectors (21475 MB) SCSI device sda: drive cache: write back sda: sda1 sda2 sda3 Attached scsi disk sda at scsi3, channel 0, id 0, lun 0 scsi: host 3 channel 0 id 0 lun1 has a LUN larger than allowed by the host adapt er scsi: host 3 channel 0 id 0 lun2 has a LUN larger than allowed by the host adapt er scsi: host 3 channel 0 id 0 lun3 has a LUN larger than allowed by the host adapt er scsi: host 3 channel 0 id 0 lun4 has a LUN larger than allowed by the host adapt er scsi: host 3...

...from=<list at someml.tld>, size=12064, nrcpt=1 (queue active) >> Mar 20 22:17:02 gaia postfix/smtpd[18941]: disconnect from some.list.server[1.2.3.4] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7 >> Mar 20 22:17:02 gaia dovecot: lmtp(18954): Error: /proc/self/status is larger than expected >> Mar 20 22:17:02 gaia dovecot: lmtp(18954): Connect from local >> Mar 20 22:17:02 gaia dovecot: lmtp(sam at samresto.dev)<18954><vbRKLa4hGWQKSgAAw1YR2w>: Error: /proc/self/status is larger than expected >> Mar 20 22:17:02 gaia dovecot: message repeated...

Hi, I have a list of vectors (of varying lengths). I'd like to sort this list by applying a function to each pair of vectors in the list and returning information to sorting routine that let's it know which one is larger. To solve problems like this in Common Lisp, the sort function accepts a function as an argument. The arguments to this function are two elements of the list which is being sorted. The writer of the function returns t (TRUE in R) when the first argument to the function is larger than the second...

...nd it took almost two full days (surprisingly, Windows ME stayed up that long without crashing) to re-encode the entire set on my 266-MHz machine. After all, in the help file Josh gives us fair warning that a couple of those options are slow. But thirty-eight of the forty-six tracks came out larger than they had in my original attempt at the -8 preset (both groups were compared after stripping all metadata and padding except STREAMINFO and SEEKTABLE). When I took the smaller version of each track, the total was still too big for a CDR without overburning -- by apparently less than 10 KB,...

...ive) > > > > > > > > Mar 20 22:17:02 gaia postfix/smtpd[18941]: disconnect from some.list.server[1.2.3.4] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7 > > > > > > > > Mar 20 22:17:02 gaia dovecot: lmtp(18954): Error: /proc/self/status is larger than expected > > > > > > > > Mar 20 22:17:02 gaia dovecot: lmtp(18954): Connect from local > > > > > > > > Mar 20 22:17:02 gaia dovecot: lmtp(sam at samresto.dev)<18954><vbRKLa4hGWQKSgAAw1YR2w>: Error: /proc/self/status is larger than e...

So I'm playing around with S3 and elasticdrive, and I create a filesystem on it with a block size larger then 4k. mkfs.xfs -b size=8k /mnt/ed5/ed0 -f This completes fine and sets up the proper filesystem. When I try to mount it, however, I get: mount /mnt/ed5/ed0 /mnt/eds35/ -o loop mount: Function not implemented looking at dmesg I get: XFS: Attempted to mount file system with blocksize 819...

...>>>>> >>>>> Mar 20 22:17:02 gaia postfix/smtpd[18941]: disconnect from some.list.server[1.2.3.4] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7 >>>>> >>>>> Mar 20 22:17:02 gaia dovecot: lmtp(18954): Error: /proc/self/status is larger than expected >>>>> >>>>> Mar 20 22:17:02 gaia dovecot: lmtp(18954): Connect from local >>>>> >>>>> Mar 20 22:17:02 gaia dovecot: lmtp(sam at samresto.dev)<18954><vbRKLa4hGWQKSgAAw1YR2w>: Error: /proc/self/status is larger th...

On Wed, Aug 02, 2017 at 11:21:56AM -0500, Andrew Walker via samba wrote: > I wrote a powershell script on a windows computer to write an ADS on a file > on a FreeBSD server with streams_xattr enabled. If it's smaller than 64KB, > it succeeds. If it's larger than 64KB, I get an "access denied message" and > powershell crashes. FreeBSD actually allows creation of large extended > attributes (at least on ZFS volumes). I've personally added ones of up to > 3MB in size, but have never actually tested the limits. oh, really? Does it...

I was reading this post http://forum.winehq.org/viewtopic.php?p=45535&sid=6957add8af3402a8afa68d8527121e2d and others like it looking for a way to make the content in the WINE window look larger. I mean to look like 800x600 resolution when the monitor settings is at 1024x768. So, I have typed this on the command line: Code: wine explorer /desktop=spider,800x600 spider.exe or wine explorer /desktop=spider,640x480 spider.exe but I see no change compare to the command line looking like thi...

...to support objects that large, C11 5.2.4.1/1 only >> requires that we support objects of size 65535! >> > > Right, the standard doesn't require it. But I guess you don't imply that > it's fine for clang to silently miscompile any program that works with > objects larger than 65535 bytes. I think that we should error when we can statically determine that an object is larger than PTRDIFF_MAX. > > > Their guidance for maximum >> object size is stated to be half of SIZE_MAX in C11 K.3.4/4 which is >> typically equivalent to PTRDIFF_MAX. >&g...

There's a discussion over on cfe-commits about how future-proof to make the C1x/C++11 atomic ABI. (http://lists.cs.uiuc.edu/pipermail/cfe-commits/Week-of-Mon-20111010/047647.html) One argument is that, because C ABI changes are painful, and processors may introduce larger atomic operations in the future, we should try to design the atomics implementation in such a way that it can take advantage of future instruction sets without needing an ABI change. The other argument (apologies if I misstate this) is that atomics larger than 2 pointers aren't useful, so we s...