Re: /proc/loadavg?
On Fri, 7 Apr 2006, Andy Greenwood wrote: Does FreeBSD have a location that stores the load average information, similarly to /proc/loadavg in Linux? I've got a php site that displays this info, but I'm not sure where to point it to. There's a linuxprocfs which you might want to mount on /compat/linux/proc, that should have waht you're after. -- jan grant, ISYS, University of Bristol. http://www.bris.ac.uk/ Tel +44 (0)117 3317661 http://ioctl.org/jan/ No generalised law is without exception. A self-demonstrating axiom. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /proc/loadavg?
Andy Greenwood wrote: Does FreeBSD have a location that stores the load average information, similarly to /proc/loadavg in Linux? I've got a php site that displays this info, but I'm not sure where to point it to. While you can mount /proc under FreeBSD, too, /proc has a bad security record and is disabled for a reason. Consider looking at the output of sysctl, instead, specificly: sysctl vm.loadavg... -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: proc filesystem
Florian Hengstberger wrote: Hi! I mounted the proc-filesystem under /proc but in contrary to Linux no additional information concerning the bus, the cpu etc. is there? Why is this? I like to cat /proc/bus/usb/devices to see if the system took notice of my usb-stick. Thanks a lot Florian try: usbdevs -v ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: proc filesystem
On Tue, Nov 30, 2004 at 01:17:19PM +0100, Florian Hengstberger typed: Hi! I mounted the proc-filesystem under /proc but in contrary to Linux no additional information concerning the bus, the cpu etc. is there? Why is this? I like to cat /proc/bus/usb/devices to see if the system took notice of my usb-stick. If you prefer to do things the Linux way, you better stick with Linux. That said; /proc is considered (and has demonstrated to be) a security risk and has therefore been disabled by default in FreeBSD 5.x Besides, *BSD's have traditionally used different mechanisms to interface with the kernel. sysctl(8) comes to mind, but there are others. In this case, dmesg will tell you if your usb-stick was recognized. So will usbdevs, as mentioned in another post. Ruben ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: proc filesystem
Ruben de Groot wrote: /proc is considered (and has demonstrated to be) a security risk and has therefore been disabled by default in FreeBSD 5.x What security risks? Same with linproc (mounted as /compat/linux/proc)? Rob. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: proc filesystem
On Wed, Dec 01, 2004 at 10:35:45AM +0900, Rob wrote: Ruben de Groot wrote: /proc is considered (and has demonstrated to be) a security risk and has therefore been disabled by default in FreeBSD 5.x What security risks? Same with linproc (mounted as /compat/linux/proc)? See any number of security advisories. It's not that there are known vulnerabilities remaining, it's that the very nature of what a procfs is means that there are likely to be other vulnerabilities waiting to be discovered. Kris pgp9Mfxe4VozA.pgp Description: PGP signature
Re: /proc
On Tue, Apr 13, 2004 at 01:56:24AM -0400, Shaun T. Erickson wrote: One of the things I really miss from my Linux system, is the /proc directory structure, where I could easily find out so much about my system and, in some cases, modify it. Is there are way I can get such a thing under FreeBSD 5.2.1-RELEASE-p4? As another person mentioned, use sysctl to change things. To view information about your system try dmesg to view the boot-up screens again. -- Stephen Fisher San Jose, CA USA ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /proc
On Tue, Apr 13, 2004 at 01:56:24AM -0400, Shaun T. Erickson wrote: One of the things I really miss from my Linux system, is the /proc directory structure, where I could easily find out so much about my system and, in some cases, modify it. Is there are way I can get such a thing under FreeBSD 5.2.1-RELEASE-p4? Read the man for procfs. It should help you figure out how to do it. Andy Miller pgp0.pgp Description: PGP signature
Re: /proc
In the last episode (Apr 13), Andy Miller said: On Tue, Apr 13, 2004 at 01:56:24AM -0400, Shaun T. Erickson wrote: One of the things I really miss from my Linux system, is the /proc directory structure, where I could easily find out so much about my system and, in some cases, modify it. Is there are way I can get such a thing under FreeBSD 5.2.1-RELEASE-p4? Read the man for procfs. It should help you figure out how to do it. Since you mentioned modifying things, you might want to look at the sysctl command instead. Linux's procfs is overloaded to do more than a /proc should. -- Dan Nelson [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /proc directory
On Wed, Dec 17, 2003 at 02:42:07PM -0800, flux wrote: What is /proc -directory for in FreeBSD? What kind of data does it store? How and for what could I use it? It's a filesystem based abstraction of the process table from the kernel. Some programs use it to get information about various processses -- although the important utilities like ps(1) just grovel directly through the kernel memory. Basically you mount it on your system, which lets a bunch of stuff work properly, and you then ignore it for ever more. Unless you're particularly concerned about security, in which case, you don't mount it and do without the stuff that needs it to run. Note that mounting the /proc directory is only a risk in the eyes of the most utterly paranoid administrators. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp0.pgp Description: PGP signature
Re: /proc directory
On Wed, Dec 17, 2003 at 12:12:18PM +, Matthew Seaman wrote: Basically you mount it on your system, which lets a bunch of stuff work properly, and you then ignore it for ever more. Unless you're particularly concerned about security, in which case, you don't mount it and do without the stuff that needs it to run. Note that mounting the /proc directory is only a risk in the eyes of the most utterly paranoid administrators. You're downplaying the security implications quite remarkably there: procfs has been the source of numerous local root vulnerabilities over the years, which should be a concern to anyone with untrusted local users. Kris pgp0.pgp Description: PGP signature
Re: /proc directory
On Wed, Dec 17, 2003 at 06:09:32AM -0800, Kris Kennaway wrote: On Wed, Dec 17, 2003 at 12:12:18PM +, Matthew Seaman wrote: Basically you mount it on your system, which lets a bunch of stuff work properly, and you then ignore it for ever more. Unless you're particularly concerned about security, in which case, you don't mount it and do without the stuff that needs it to run. Note that mounting the /proc directory is only a risk in the eyes of the most utterly paranoid administrators. You're downplaying the security implications quite remarkably there: procfs has been the source of numerous local root vulnerabilities over the years, which should be a concern to anyone with untrusted local users. Hmmm... On reflection, and after reading through the list of security advisories, then yes. It is entirely possible that there still exist vulnerabilities in the /proc system and you shouldn't use it on a multi-user system where you don't trust all of the users. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp0.pgp Description: PGP signature
Re: /proc directory
What is /proc -directory for in FreeBSD? What kind of data does it store? How and for what could I use it? It is a psuedo file system that the system uses while running for process information. You should be able to find information on it in the handbook and by searching. jerry -- Best regards, flux mailto:[EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Proc Size Mismatch
On Mon, Aug 25, 2003 at 07:14:03PM +0200 or thereabouts, Ian Barnes wrote: Hi, I am running a 4.7 stable machine on a p1 120. With 16meg of ram. ITs function is a secondary DNS server. IT has been running very stable until this weekend. The machine froze for some or other reason. Upon reboot, i was told it couldnt FSCK the drives and I had to do it manually. Okay, cool, fine, no problem, did it manually, and got it to boot. Now when i login and try and type something, these are the errors im getting: [ ... ] userland out of sync with kernel, recompile libkvm etc ^^ [ ... ] Any ideas anyone ? Do i need to format and reload ? What can i do to help this? RTS -- and buildworld/installworld. -- Josh Ian P.S. Oh, i was doing a buildworld when i froze! Weird. Try re-cvsupping maybe. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: proc filesystem error
On Sun, Jul 27, 2003 at 05:59:57PM +0530, Shantanu Mahajan wrote: i am getting following error # killall squid proc size mismatch (47880 total, 1056 chunks) userland out of sync with kernel, recompile libkvm etc Userland not in sync with kernel. FAQ. -- Jonathan Chen [EMAIL PROTECTED] We laugh in the face of danger, we drop icecubes down the vest of fear - Edmond Blackadder III ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: proc size mismatch (73920 total, 1060 chunks)
On Thu, 20 Feb 2003, Dean Gunther wrote: I keep getting the above error when I try to do things like ps or even top. I have looked at everyting I can think of, but haven't been able to figure out what is wrong. I tried rebooting the server, but to no avail. Any ideas would be greatly appreciated. Did you rebuild world and / or kernel, without doing both? That's the most common reason for that particular error. - Jeff Jirsa To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: proc size mismatch
On Monday 03 February 2003 08:41 am, Harold Mackey wrote: It appears that my kernel is 4.7-STABLE and cvsup has downloaded 4.7-RELEASE-pl2. I need to get my system synced up again and STABLE. Any how-to's out there? There isn't a tag for 4.7-stable. It is only RELENG_4 and slides with new releases. Kent Thanks Harold A. Mackey MUSC Digestive Disease Center 96 Jonathan Lucas Street Suite 210 CSB Charleston, SC 29403 ph 843-792-4858 fx 843-792-4184 -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: proc size mismatch
Harold Mackey wrote: It appears that my kernel is 4.7-STABLE and cvsup has downloaded 4.7-RELEASE-pl2. I need to get my system synced up again and STABLE. Any how-to's out there? The handbook's section on staying current. When you cvsup again, you should use RELENG_4 instead of RELENG_4_7 for your tag. The former is -STABLE, the latter is the -RELEASE security updates. -- Bill Moran Potential Technologies http://www.potentialtech.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
