#ifdef linux

Another procenv release that is bringing the OSX version up to parity. Also, thanks to harens , procenv is now available in MacPorts ! If anyone knows about querying IPC details on Darwin (via Mach?), please comment on the GitHub issue (or raise a PR :)

(Lots of) new procenv release(s)   procenv is now at version 0.55 . Significant changes since version 0.46 : FreeBSD and Hurd fixes. Show if running in a VM. --memory now shows more memory details. More capabilities. PROCENV_EXEC fixes. Further details on the release page .

I have just released procenv version 0.46 . Although this is a very minor release for the existing platforms (essentially 1 bug fix), this release now introduces support for a new platform... Darwin Yup - OS X now joins the ranks of supported platforms. Although adding support for Darwin was made significantly easier as a result of the recent internal restructure of the procenv code, it did present a challenge: I don't own any Apple hardware. I could have borrowed a Macbook, but instead I decided to see this as a challenge: Could I port procenv to Darwin without actually having a local Apple system?  Well, you've just read the answer, but how did I do this? Stage 1: Docker Whilst surfing around I came across this interesting docker image: https://hub.docker.com/r/andrewd/osxcross/ It provides a Darwin toolchain that I could run under Linux. It didn't take very long to follow my own instructions on porting procenv to a new platform . But although I...

Yesterday, I released procenv 0.45 . Although not a huge amount has changed on the outside in this release, rather dramatic changes have occurred on the inside, as evinced by the following: $ git diff 0.44..0.45 --stat|grep "src / .*\.[ch] "  src/messages.h                          |    41 +  src/output.c                            |  2001 ++++++  src/output.h                            |   179 +  src/platform-headers.h                  |   243 + ...

(Cough... This should probably be called the " I-almost-forgot-I-had-a-blog release "! :-) Development has now moved to github: https://github.com/jamesodhunt/procenv So you can grab the release files here: https://github.com/jamesodhunt/procenv/releases The move to github brings a few advantages, including Travis-CI integration: https://travis-ci.org/jamesodhunt/procenv (btw - does anyone know of a CI solution for FreeBSD?) Even more awesome being that, thanks to the wonder of webhooks, procenv is now building for lots of distros. Take a look at: https://build.opensuse.org/package/show/home:jamesodhunt:procenv/procenv So you get to see the environment those builds run in and OBS is also providing procenv packages! Here's the funky download page (just click your distro): https://software.opensuse.org/download.html?project=home%3Ajamesodhunt%3Aprocenv&package=procenv Caveat emptor: those packages are building off the tip, so are not nec...

Earlier today I released procenv 0.34 . Quite a bit has changed since version 0.27 including: Recognises AARCH64, SuperH (fix), PPC64, PPCspe, PPC64LE, OpenRISC systems. Added symbolic names in ' --ranges '. Displays Linux binary personality (and flags). Improved ' --capabilities ' output showing not only bounding set, but also whether each capability is supported, permitted, effective and inheritable values. Added ' --memory ' which shows NUMA memory details. Added ' --cpu ' which displays CPU affinity details. Added rpm spec file allowing it to build on RHEL5, Fedora, etc . Improved ' --sizeof ' which now shows lots more standard types. Displays FreeBSD Capsicum capabilities. Lots of fixes. Version 0.34 is now available in Debian sid whilst Ubuntu Trusty will be released with procenv 0.33 (which lacks the binary personality information). Take a look at the links on the main procenv page to see the different environments that it...

Procenv 0.27 has been released. This release introduces a raft of new features... IPC  It is now possible to display details of the following IPC mechanisms: message queues semaphores shared memory Alas, this feature is not available on BSD's as yet partly since there appears to be no documented way to query these mechanisms. Output Categories The introduction of the IPC categories brings the total number of output categories to 32: meta arguments capabilities cgroups clocks compiler confstr environment file descriptors libraries limits locale misc message queues mounts network oom platform process ranges rusage semaphores shared memory signals sizeof stat sysconf threads time timezone tty uname Highly-Structured Output The code that handles procenv has been completely rewritten so that all output is highly structured. So, rather than displaying file descriptors like this: $ procenv --fds fds: fd 0: terminal=yes ('/dev...

Version 0.26 of the procenv utility is now available. Changes: Check to determine if running on a console now works for FreeBSD/kFreeBSD too. Added ability to show all arguments ( -A / --arguments ) (useful when using --exec ). Added ability to display network details ( -N / --network ). Added BSD/Hurd-specific signals. Corrected output sort order. Mount details now include block, inode and fsck details. There are now 29 categories of environment information displayed when procenv is run (on Linux). Grab it from: https://launchpad.net/procenv/ This update should appear in Debian, Ubuntu and FreeBSD soon...

Procenv 0.25 now builds natively under Android: https://launchpad.net/procenv/ It also fixes an interesting issue that was causing it to fail to generate FreeBSD build logs. However, that is now fixed so you can see the FreeBSD build environment now too by looking at the port logs: http://pointyhat.freebsd.org/errorlogs/i386-8-latest-logs/procenv-0.25.log http://pointyhat.freebsd.org/errorlogs/i386-9-latest-logs/procenv-0.25.log   More logs to come - the FreeBSD ports seem to build rather slowly...)

If you're interested in seeing the initial environment inside an LXC container, here's how: Install procenv inside the container: $ sudo apt-get install -y procenv Shutdown the container: $ sudo shutdown -h now Boot the container (mine is called " raring " in this example) like this: $ sudo lxc-start -n raring --console-log /tmp/lxc-console.log \ -- /usr/bin/procenv --file=/dev/console --exec \ -- /sbin/init --debug View the /tmp/lxc-console.log logfile in the host environment. Note that those two sets of non-option double-dashes are required; the first tells LXC to treat what follows as a command to run after the container starts (in this case procenv ), and the second set tells procenv to treat what follows as a command to run after it has finished running (in this case Upstart ( /sbin/init :-))!

The procenv utility covered in a previous post is now at version 0.15 and also available in Debian Sid and Ubuntu Raring . So, you can do the usual " sudo apt-get install procenv " followed by simply " procenv " to run it. However, due to the way this utility is built, there is a little more you can do. Read on... procenv runs itself as part of its build (at the end of course :-). What this means is that you can now see what that build environment is like by looking at the build logs: Debian build logs Ubuntu build logs (you need to expand the "twistie" to see the log files. If you haven't already heard, for the Ubuntu Raring cycle, autopkgtest ( DEP-8 ) tests -- where package builds automatically trigger tests that run on an environment very similar to a "normal" system -- are a hot topic. procenv is DEP-8 enabled, so again, we get to see exactly what such an autopkgtest environment provides . With this information, you can...

Changes: expanded man page, more sizeof types shown and resource usage details added. Code is available here: https://launchpad.net/procenv If anyone is interested in contributing patches for the following, let me know: code to show network details. support for other platforms (I'd like to add AIX, HP-UX, Solaris, i5O/S, MVS/zO/S, VMS) but no longer have access to such systems).