Home > Cannot Use > Cannot Use Procfs In The

Cannot Use Procfs In The

mount chroot share|improve this question asked Aug 20 '10 at 17:57 Brian 6327 add a comment| 2 Answers 2 active oldest votes up vote 3 down vote accepted Linux refuses to And a quick test shows:% grep off_t /usr/include/sys/procfs.hoff_t pio_offset; /* virtual address in target process */In other words, if you use lfcompile, then the priovec_t structure nolonger matches between what you're This is an alternative to @@ -16,11 +16,14 @@ # Inputs: # - SRC-DIR-NAME is the source directory, relative to $srcdir. # - BUILD-DIR-NAME is `top-build -> build' +# - EXTRA-ARGS stdarg and printf() in C What would be the consequences of a world that has only one dominant species of non-oceanic animal life? weblink

Please contact us immediately if you are not the intended recipient of this communication, and do not copy, distribute, or take action relying on it. Yes, /proc and, by extension, still exist. But I am a Mac OS X user and I cant find /proc folder in my machine. For instance: [email protected]_:~$ sudo umount -n /proc/ [sudo] password for _: umount: /proc: device is busy. (In some cases useful info about processes that use the device is found by lsof(8) https://sourceware.org/ml/gdb-patches/2014-12/msg00058.html

This is sub-optimal for us, for example reading /proc entries for 64-bit processes doesn't work when collectd is 32-bit. You should unmount the none filesystem mounted at /proc with umount /proc then rmdir /proc . Sign in to comment Contact GitHub API Training Shop Blog About © 2016 GitHub, Inc.

  • up vote 14 down vote favorite 10 I am reading a book that speaks about Bash in Linux systems.
  • It's not a must-have.
  • gdb (and only gdb AFAIK) uses procfs, and Solaris procfs doesn't support a largefile environment, no idea why? has #if !defined(_LP64) && _FILE_OFFSET_BITS == 64 #error "Cannot use procfs in
  • For a 64-bit default gcc, one needs 64-bit nm etc.
  • sudo mount -o bind /proc /proc When I found I no longer needed it, I quite stupidly rm -r 'd it.
  • It also might make sense to think ofboth 32-bit and 64-bit versions of the OS itself (still present on x86,and present at one time for SPARC, which is only 64-bit now).
  • The correct way is to compile in 64 bit, however, from my work as a downstream packager, configure should not set -m32 or -m64, that should be to the discretion of
  • I'm still a bit curious as towhat the underlyingreason for #error above is.AFAIK, procfs was created in such a way that a 64-bit processcan monitor anything (given appropriate permissions), but a
  • collectd member octo commented Jun 11, 2015 We can likely steal this from src/swap.c: /* avoid swap.h error "Cannot use swapctl in the large files compilation environment" */ #if HAVE_SYS_SWAP_H &&
  • So don't. ;-}--James Carlson 42.703N 71.076W Giovanni Tirloni 2011-01-20 12:52:54 UTC PermalinkRaw Message Post by David BartleyI want to use procfs.h while having large filesupport; there's a few#if !defined(_LP64) &&

Alex Am 16.12.2006, 06:08 Uhr, schrieb John Vandenberg : > Hi, > > On 12/16/06, Stipe Tolj wrote: >> Andrikopoulos Dimitrios wrote: >> >> > Hello, What crime would be illegal to uncover in medieval Europe? Please contact us immediately if you are not the = intended > recipient of this communication, and do not copy, distribute, or take > action > relying on it. The packager can then decide to add -m64 or disable the plugin during the compilation if needed.

I don't think we need largefile support for anything accessed by host.h. It's deprecated. So, I think priovec_t needs toalways be 12 bytes regardless of whether or not large file support isenabled or disabled.Post by Robert ThurlowBacking up, what problem are you trying to solve?I Why is (a % 256) different than (a & 0xFF)?

Of course, rm refused to remove /proc. share|improve this answer answered Aug 20 '10 at 18:13 vmfarms 2,609913 Thanks. Please don't fill out this field. Browse other questions tagged osx or ask your own question.

The cost of switching to electric cars? https://www.illumos.org/issues/2410 I have added extra 64 bit builds in buildbot to take care of checking these issues. dago commented Jun 11, 2015 All Solaris 10+ hosts and all Sparc hosts on the farm run a 64 bit kernel. Any communication received in error, or subsequent = reply, > should be deleted or destroyed. >=20 >=20 >=20 > ------------------------------------------------------- > This SF.net email is sponsored by: > The Definitive IT

I'm still a bit curious as to what the underlyingreason for #error above is.-- David Richard L. And actually, I did try to unmount /proc. it's equivalent to lsof +f -- /proc), whether through the chroot or outside (mount --bind is peculiar sometimes). YA novel involving immortality via drowning more hot questions question feed about us tour help blog chat data legal privacy policy work here advertising info mobile contact us feedback Technology Life

How were Lisps usually implemented on architectures that has no stack or very small stacks? M=E4rz 2003 00:27 > An: Net-Snmp-Coders (E-mail) > Betreff: Solaris Large File Compilation Environment and Perl >=20 > I believe I've found a better solution to our problems with net-snmp = Any communication received in error, or subsequent reply, should be deleted or destroyed. check over here Authentication-results: sourceware.org; auth=none References: <20141203104812 dot GA14666 at adacore dot com> This patch mostly aims at fixing a GDB build failure on 32bit Solaris systems (Sparc and x86), due to a

Why is the reduction of sugars more efficient in basic solutions than in acidic ones? Index Nav: [DateIndex] [SubjectIndex] [AuthorIndex] [ThreadIndex] Message Nav: [DatePrev][DateNext] [ThreadPrev][ThreadNext] Other format: [Raw text] [RFA] configure gdb/gnulib with --disable-largefile if largefile support disabled. The directory /proc still exists, though. –Brian Aug 24 '10 at 13:15 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google

All rights reserved. */ +/* + * Copyright (c) 2012, Joyent, Inc.

So unless the user explicitly requested # large-file support through the --enable-largefile switch, disable # large-file support in favor of procfs support. For those reasons, it's much more work to provide a working slim LTO environment (and that's not only true on Solaris, but also on Linux where I often test a recent dago commented Jun 11, 2015 Yes, since Solaris 10 the kernel is 64 bit on x86 and Solaris 11 does not even offer 32 bit, but as Solaris has a 32 Because the kernel does magically return appropriate structs from /proc to 32bit and 64bit binaries, this will work okay.

Rainer Comment 3 Rainer Orth 2011-11-21 16:41:54 UTC It took me a while, but the issue turned out to be different: * Toplevel config/largefile.m4 disables largefile support for 32-bit Solaris, and gdb/ChangeLog: * acx_configure_dir.m4 (ACX_CONFIGURE_DIR): Add support for new "EXTRA-ARGS" parameter. * configure.ac: If large-file support is disabled in GDB, pass --disable-largefile to ACX_CONFIGURE_DIR call for "gnulib". * configure: Regenerate. If you enable large file support for 32-bit (_ILP32) code,priovec_t ends up being 16 bytes, while the "native" size is 12 bytes.However, I believe the kernel always sees the 12 byte this content If even umount -n /proc doesn't work, it's probably because some process is still running inside the chroot to access it.

How do I unmount it, now? Thread view RE: Solaris Large File Compilation Environment and Perl From: Stefan Radman - 2003-03-25 20:07:17 What about procfs? $ uname -srpi SunOS 5.9 sparc SUNW,UltraSPARC-IIi-cEngine $ grep '#error' /usr/include/sys/* Please don't fill out this field. We need to build gnulib under some other # directory not "gnulib", to avoid the problem of both GDB and # GDBserver wanting to build it in the same directory, when

All rights reserved. + */ + #include #include #include @@ -935,7 +939,7 @@ pr_control32(int32_t cmd, arg32_t *argp, prnode_t *pnp, cred case PCREAD: /* read from the address space Hamilton 2011-01-21 20:09:12 UTC James Carlson 2011-01-21 20:26:16 UTC Giovanni Tirloni 2011-01-20 12:52:54 UTC about - legalese Loading... Be There! > NetWorld+Interop Las Vegas 2003 -- Register today! > http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en > _______________________________________________ > Net-snmp-coders mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/net-snmp-coders RE: Solaris Large File Compilation Environment and Perl From: Do I understand this correctly that the only time we will have problems is when we run a 32bit collectd binary on a 64bit kernel?

The warning would be perfect. Any communication received in error, or subsequent = reply, > should be deleted or destroyed. >=20 >=20 >=20 > ------------------------------------------------------- > This SF.net email is sponsored by: > The Definitive IT Taking what you wrote at face value, you tried to unmount /proc, not /proc. We can't use AC_CONFIG_SUBDIRS as that'd expect # to find the the source subdir to be configured directly under # gdbserver/.

Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the

Back to Top