similar to: procfs + chmod = no go

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

I''m running the latest mongrel (1.0.1) and the latest mongrel_cluster (1.0.1.1) on FreeBSD 6.1. When I use capistrano to try to stop or restart my cluster I get this (partial) output: ps: Process environment requires procfs(5) And my Mongrel processes haven''t stopped. Any ideas? Thanks, Jamie

-----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:

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

Hello everyone... :) I liked the idea of having descriptions for various sysctl oid's in -CURRENT, so I have created a patch to merge these over to -STABLE. I am unsure as to how much work has already gone into bringing this to -STABLE, but as the descriptions already exist in the source, I am fairly confident that it was planned at some point. All I can really ask is that someone with more

-----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:

Author: peterte Repository: /hg/zfs-crypto/gate Revision: b681de1a640aeda1c2465325a301eec62c555cef Log message: 6324745 vmem memory leak in the procfs PAGEDATA subsystem. 6329403 hrm_init() cannot ever return -1 but in various places we check for that. 6330765 procfs pagedata can panic machine. Files: update: usr/src/uts/common/vm/hat_refmod.c

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-03:17.procfs Security Advisory The FreeBSD Project Topic: kernel memory disclosure via procfs Category: core Module: sys Announced:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-03:17.procfs Security Advisory The FreeBSD Project Topic: kernel memory disclosure via procfs Category: core Module: sys Announced:

-----BEGIN PGP SIGNED MESSAGE----- ============================================================================= FreeBSD-SA-00:77 Security Advisory FreeBSD, Inc. Topic: Several vulnerabilities in procfs Category: core Module: procfs Announced: 2000-12-18

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

Here is my scenario: I have two directories that have their access controlled by secondary groups of the users. \\server\coolguys is available to the group 'admins' while the directory \\server\averagejoes is accessible to the group 'lusers'. I have a user, we'll call him joe, that is primarily in the admins group, but is also in lusers. If joe is to copy a directory or a

Hi Ralph, In reviewing the wiki editing guidelines, I see that I'm supposed to setup a Personal Homepage, but I'm not allowed to edit that page. Thanks, Sean

I'm trying to get veracity (http://www.rocksoft.com/veracity/), a tripwire replacement, working on FreeBSD 5.x. When I try and create a snapshot I get the following error for files sitting on my root partition: -- snip snip -- csh.logout E: Error opening binary (B) stream of file "/etc/csh.logout". (OS error message="File is on the procfs (/proc)

I looked on google for some time and haven't found a source for 9-911 labels to attach to phones. I have run into them in the past but I can't currently find a source. I am looking for a low volume were having them printed up for me would not be economical. Any suggestions would be welcome. Thanks -Jason -- ----------------------------------------------------------------------------

With some progress in PowerManagement support (there's a patch nearly done for reading the P-tables, written mostly by xexaxo, derived from thunderbirds nvclock, with 0x40 adjustments from myself) in my opinion it's time to think about the user aspect of this. My personal idea for GPU scaling was similar to that of CPU scaling in appearance eventually. When you look at the cpufreq-applet

Hi! On BSD, mmap()ing files works on on-disk files but not on pseudo filesystems like kernfs or procfs. Therefore, attached patch mmap()s anonymous memory. Linux equivalents are sysfs and procfs to above BSD''s pseudo-filesystems. On Linux, mmap is implemented for sysfs but it is questionable to me how write operations work since (most) files in sysfs have static content. So this patch

Running freeBSD 6.1 After changing chkrootkit to the latest version V. 0.47 and compiling it then running it I get the following: ==================<SNIPPIT>================ Searching for anomalies in shell history files... nothing found Checking `asp'... not infected Checking `bindshell'... INFECTED (PORTS: 6667) Checking `lkm'... You have 131 process hidden for readdir