similar to: 6324745 vmem memory leak in the procfs PAGEDATA subsystem.

I was wondering if a fork failure with EAGAIN will manifest as an allocation failure in vmem, if so how to see that and if there is a specifc cache that can be tweaked. At present the only cache that is reporting any failure is kmem_lp 1002438656 1002438656 239 1858 thanks -- This message posted from opensolaris.org

On Tue, Jun 25, 2013 at 7:07 PM, Daniel P. Berrange <berrange@redhat.com>wrote: > On Tue, Jun 25, 2013 at 07:02:40PM +0200, Roland Giesler wrote: > > System: > > $ cat /etc/issue > > Ubuntu 12.10 \n \l > > > > $ uname -a > > Linux Matt-HP 3.5.0-34-generic #55-Ubuntu SMP Thu Jun 6 20:20:19 UTC 2013 > > i686 i686 i686 GNU/Linux > > > >

Author: peterte Repository: /hg/zfs-crypto/gate Revision: 3ba32c5bc9459959256eb41efe4324aff24953d0 Log message: 6259653 cp command fail to copy 3.2 GB flash archive from DVD in S9/S10 32 bit x86 system. Files: update: usr/src/uts/common/fs/hsfs/hsfs_vnops.c update: usr/src/uts/common/sys/fs/hsfs_spec.h

Author: peterte Repository: /hg/zfs-crypto/gate Revision: c58eb973cf010ce6ff943f2be951de2ee68f4b8e Log message: 5069845 hsfs_read induces panic by calling segmap_getmapflt with bad length parameter 5089882 hsfs_read is inconsistent. Files: update: usr/src/uts/common/fs/hsfs/hsfs_vnops.c

Author: peterte Repository: /hg/zfs-crypto/gate Revision: 5ae0e5bf22a4fae868a0917839f732060ad9a687 Log message: 4766208 alarm(2) does not work with arguments larger than 2^31/100 on Solaris 2.6 thru Nevada. Files: update: usr/src/uts/common/syscall/alarm.c

System: $ cat /etc/issue Ubuntu 12.10 \n \l $ uname -a Linux Matt-HP 3.5.0-34-generic #55-Ubuntu SMP Thu Jun 6 20:20:19 UTC 2013 i686 i686 i686 GNU/Linux I have a converted VMWare virtual machine which I converted by using: $ vmware2libvirt -f ./WinXPPro.vmx > WinXPPro.xml $ virsh -c qemu:///system define WinXPPro.xml After various efforts to start the machine, I changed some of the

Dear all, please could you advise me on the following : I've written a R script that reads 3 arguments from the command line, i.e. : " args <- commandArgs(TRUE) TUMOR <- args[1] GERMLINE <- args[2] CHR <- args[3] ". when I submit the R script to a PBS HPC scheduler, I do the following (below), but ... I am getting an error message. (I am not posting the error message,

This sounds like an operating system specific question, in that "submit the R script to a PBS HPC scheduler" would be the kind of action that would run R with very different environment variables and possibly different access credentials than your usual interactive terminal. A thorough reading of the "Installation and Administration Guide" and some study of your HPC

A lot of people in the security community, myself included, are interested in memory forensics these days. Virtualization is a natural fit with memory forensics because it allows one to get access to a guest's memory without having to introduce any extra software into the guest or otherwise interfere with it. Incident responders are particularly interested in getting memory dumps from

Hi, The problem is most likely, you need to call a R CMD BATCH with your arguments and the R-script inside of a shell script that you submit to your qsub. Unfortunately we don't use qsub anymore so can't test it, but it should be as follows: R-script eg. test.R: > ##First read in the arguments listed at the command line > args=(commandArgs(TRUE)) > > ##args is now a list of

Ok, so i did some tests. find /path -type f -ls > /dev/null First on my local SSD disk (1.9 millions files) : 1 find : real 2m16.743s user 0m7.607s sys 0m45.952s 10 concurrent finds (approx same results for each) : real 4m48.629s user 0m11.013s sys 2m0.288s Almost double time is somehow logic. Now same test on my server on the iSCSI disk (when there is no other activity) (2.8 millions

I create a new thread, because the issue is not really the same, but i copy here the thread that made me jump into the list. My issue is not really that it waits before starting copying, but a general performance issue, specially when there are multiple rsync running at the same time. Here is my situation : I have multiple clients (around 20) with users and i want to rsync their home dirs with

I know this has been brought up before but I''m receiving the error ... Process environment requires procfs(5) ... when trying to restart my cluster. I''ve narrowed it down to ''find_pid'' method in init.rb. I''m running a FreeBSD 6.2 server and mongrel_cluster version 1.0.5. The command that gives me the error is ... ps -ewwo pid,command ... but

Hi all, I am using libvirt:qemu-kvm and I want to access(RO) the procfs of the guest vm. I was trying to use guestfs for the same purpose. I can access /tmp of the guest but not the /proc Is it a known issue? If so, how can I overcome the same? Any pointers? Snippet> [root@hv285 scoreboards]# virsh list Id Name State

running 4.8 stable, the cmdline file in /proc/$$ seems to be trucated at, or before 256 bytes for very long command lines. I cant find any refernec to this behaviour in the manpage, nor does google reveal anything. I took a look in the source, but didnt properly understand what was going on - the comments imply that it does give the full commandline for the current process, however. any

Hi all, I am using libvirt:qemu-kvm and I want to access(RO) the procfs of the guest vm. I was trying to use guestfs for the same purpose. I can access /tmp of the guest but not the /proc Is it a known issue? If so, how can I overcome the same? Any pointers? Snippet> [root@hv285 scoreboards]# virsh list Id Name State

I recently did a backport of a couple of networking bug fixes from s10x_u4_b6 to s10x_u3_b10. I patched just /platform/i86pc/kernel/unix and /platform/i86pc/kernel/amd64/unix in my existing u3 OS image and I''m seeing this dtrace problem when running any dtrace script: NODE hcb101 ~ $ ./tcpstat.sh dtrace: failed to compile script /dev/fd/10: "/usr/lib/dtrace/procfs.d", line

Dear all: In dtrace.c, function dtrace_probe_create(), there''re a piece of code: id = (dtrace_id_t)(uintptr_t)vmem_alloc(dtrace_arena, 1, VM_BESTFIT | VM_SLEEP); id is uint32_t, and I think id is used as an index to array dtrace_probes[] but why not just use id = cur_value + 1, cur_value is a global variable to record the lastest id? Is this a trick? for what? Thanks :)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-04:17.procfs Security Advisory The FreeBSD Project Topic: Kernel memory disclosure in procfs and linprocfs Category: core Module: sys Announced:

Hello, I was wondering if it was possible to limit user access on /proc without having to use securelevels. For some reason chmod 751 /proc (or 750) does nothing. Is this possible on FreeBSD 4.9 ? Can't find anything about it in the manual pages. Just want to prevent lusers from running: for file in /proc/*/cmdline; do cat $file; echo; done Greetz, Jimmy Scott