acct v3 support
Are there plans to have more architectures enable the newer accounting file format via CONFIG_BSD_PROCESS_ACCT_V3 ? I'm actually only interested in amd64. $ egrep 'CONFIG_BSD_PROCESS_ACCT_V3=y|linux-2.6-2.6.12/debian/arch/' \ linux-2.6_2.6.12-5.diff The above seems to indicate that v3 is enabled for alpha and hppa. I realize enabling this feature may require changes in the user space tools, e.g. http://www.physik3.uni-rostock.de/tim/kernel/utils/acct/ Should I file a wishlist bug? (Please Cc me responses as I'm not on the list.) Thanks for your time, Ryan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: acct v3 support
On Wed, Sep 07, 2005 at 02:57:47PM -0700, Ryan Lovett wrote: > Are there plans to have more architectures enable the newer accounting file > format via CONFIG_BSD_PROCESS_ACCT_V3 ? I'm actually only interested in > amd64. > > $ egrep 'CONFIG_BSD_PROCESS_ACCT_V3=y|linux-2.6-2.6.12/debian/arch/' \ > linux-2.6_2.6.12-5.diff > > The above seems to indicate that v3 is enabled for alpha and hppa. I > realize enabling this feature may require changes in the user space tools, > e.g. http://www.physik3.uni-rostock.de/tim/kernel/utils/acct/ > > Should I file a wishlist bug? > > (Please Cc me responses as I'm not on the list.) I don't see any reason why they should be enabled for alpha and hppa while disabled for other arches. It should be either on or off universaly, right? Well, possibly with the exception of arm and some flavours of other architectures that seem to have fairly minimal configs. Does anyone know of any reason why this should not be made so? -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: acct v3 support
On Thu, Sep 08, 2005 at 11:09:33AM +0900, Horms wrote: > On Wed, Sep 07, 2005 at 02:57:47PM -0700, Ryan Lovett wrote: > > Are there plans to have more architectures enable the newer accounting file > > format via CONFIG_BSD_PROCESS_ACCT_V3 ? I'm actually only interested in > > amd64. > > > > $ egrep 'CONFIG_BSD_PROCESS_ACCT_V3=y|linux-2.6-2.6.12/debian/arch/' \ > > linux-2.6_2.6.12-5.diff > > > > The above seems to indicate that v3 is enabled for alpha and hppa. I > > realize enabling this feature may require changes in the user space tools, > > e.g. http://www.physik3.uni-rostock.de/tim/kernel/utils/acct/ > > > > Should I file a wishlist bug? > > > > (Please Cc me responses as I'm not on the list.) > > I don't see any reason why they should be enabled for alpha and hppa > while disabled for other arches. It should be either on or > off universaly, right? Well, possibly with the exception of > arm and some flavours of other architectures that seem to have > fairly minimal configs. > > Does anyone know of any reason why this should not be made so? I have attached two patches, in relation to use. Pick one :) 1. bsd_process_acct_v3-off.patch Turn BSD_PROCESS_ACCT_V3 Off This consolidates the BSD_PROCESS_ACCT configuration so that it is enabled for all flavours of all architectures, except for sparc and arm/rpc, arm/s3c2410 - can someone who knows confirm that is supposed to be the case. It also consolidates the BSD_PROCESS_ACCT_V3 configuration and disables it for all flavours of all architectures. The net-result of this patch, apart from the consolidation, is that BSD_PROCESS_ACCT_V3 is now disabled for hppa and alpha. 2. bsd_process_acct_v3-on.patch Turn BSD_PROCESS_ACCT_V3 On As per bsd_process_acct_v3-off.patch, This consolidates the BSD_PROCESS_ACCT configuration so that it is enabled for all flavours of all architectures, except for sparc and arm/rpc, arm/s3c2410 - can someone who knows confirm that is supposed to be the case. It also consolidates the BSD_PROCESS_ACCT_V3 configuration and enables it for all flavours of all architectures that have BSD_PROCESS_ACCT enabled. The net-result of this patch, apart from the consolidation, is that BSD_PROCESS_ACCT_V3 is enabled for amd64, arm/footbridge, arm/ixp4xx, i386, ia64, m68k, powerpc and s390. -- Horms diff --exclude .svn -ruN a/debian/arch/alpha/config b/debian/arch/alpha/config --- a/debian/arch/alpha/config 2005-09-01 12:52:29.0 +0900 +++ b/debian/arch/alpha/config 2005-09-08 12:56:55.0 +0900 @@ -4,8 +4,6 @@ CONFIG_GENERIC_ISA_DMA=y # CONFIG_GENERIC_IOMAP is not set CONFIG_CLEAN_COMPILE=y -CONFIG_BSD_PROCESS_ACCT=y -CONFIG_BSD_PROCESS_ACCT_V3=y # CONFIG_AUDIT is not set # CONFIG_KOBJECT_UEVENT is not set # CONFIG_IKCONFIG is not set diff --exclude .svn -ruN a/debian/arch/amd64/config b/debian/arch/amd64/config --- a/debian/arch/amd64/config 2005-09-01 12:52:30.0 +0900 +++ b/debian/arch/amd64/config 2005-09-08 12:56:55.0 +0900 @@ -7,8 +7,6 @@ CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_CLEAN_COMPILE=y -CONFIG_BSD_PROCESS_ACCT=y -# CONFIG_BSD_PROCESS_ACCT_V3 is not set CONFIG_AUDIT=y # CONFIG_AUDITSYSCALL is not set CONFIG_KOBJECT_UEVENT=y diff --exclude .svn -ruN a/debian/arch/arm/config.footbridge b/debian/arch/arm/config.footbridge --- a/debian/arch/arm/config.footbridge 2005-09-01 12:52:29.0 +0900 +++ b/debian/arch/arm/config.footbridge 2005-09-08 12:56:55.0 +0900 @@ -25,8 +25,6 @@ CONFIG_SWAP=y CONFIG_SYSVIPC=y # CONFIG_POSIX_MQUEUE is not set -CONFIG_BSD_PROCESS_ACCT=y -# CONFIG_BSD_PROCESS_ACCT_V3 is not set CONFIG_SYSCTL=y # CONFIG_AUDIT is not set # CONFIG_HOTPLUG is not set diff --exclude .svn -ruN a/debian/arch/arm/config.ixp4xx b/debian/arch/arm/config.ixp4xx --- a/debian/arch/arm/config.ixp4xx 2005-09-01 12:52:29.0 +0900 +++ b/debian/arch/arm/config.ixp4xx 2005-09-08 12:56:55.0 +0900 @@ -25,8 +25,6 @@ CONFIG_SWAP=y CONFIG_SYSVIPC=y # CONFIG_POSIX_MQUEUE is not set -CONFIG_BSD_PROCESS_ACCT=y -# CONFIG_BSD_PROCESS_ACCT_V3 is not set CONFIG_SYSCTL=y # CONFIG_AUDIT is not set # CONFIG_HOTPLUG is not set diff --exclude .svn -ruN a/debian/arch/config b/debian/arch/config --- a/debian/arch/config2005-09-01 12:52:30.0 +0900 +++ b/debian/arch/config2005-09-08 12:56:55.0 +0900 @@ -178,3 +178,5 @@ CONFIG_TCG_NSC=m # CONFIG_IP_ROUTE_MULTIPATH_CACHED is not set CONFIG_6PACK=m +# CONFIG_BSD_PROCESS_ACCT_V3 is not set +CONFIG_BSD_PROCESS_ACCT=y diff --exclude .svn -ruN a/debian/arch/hppa/config b/debian/arch/hppa/config --- a/debian/arch/hppa/config 2005-09-01 12:52:30.0 +0900 +++ b/debian/arch/hppa/config 2005-09-08 12:56:55.0 +0900 @@ -27,8 +27,6 @@ CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_POSIX_MQUEUE=y -CONFIG_BSD_PROCESS_ACCT=y -CONFIG_BSD_PROCESS_ACCT_V3=y CONFIG_SYSCTL=y # CONFIG_AUDIT is not set
Re: acct v3 support
On Wed, Sep 07, 2005 at 02:57:47PM -0700, Ryan Lovett wrote: > Are there plans to have more architectures enable the newer accounting file > format via CONFIG_BSD_PROCESS_ACCT_V3 ? I'm actually only interested in > amd64. > > $ egrep 'CONFIG_BSD_PROCESS_ACCT_V3=y|linux-2.6-2.6.12/debian/arch/' \ > linux-2.6_2.6.12-5.diff > > The above seems to indicate that v3 is enabled for alpha and hppa. I > realize enabling this feature may require changes in the user space tools, > e.g. http://www.physik3.uni-rostock.de/tim/kernel/utils/acct/ > > Should I file a wishlist bug? This breaks the accounting format, so it's a change that needs a lot of thought. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: acct v3 support
On Fri, Sep 09, 2005 at 04:50:03PM +0200, Christoph Hellwig wrote: > This breaks the accounting format, so it's a change that needs a lot > of thought. Okay, thanks for considering this. The file http://www.physik3.uni-rostock.de/tim/kernel/utils/acct/readme.txt mentions: Note that the --raw option of dump-acct makes for a nice little format converter together with the new --format and --byteswap options, if multiformat support is compiled in. It works in any direction, which particularly means you don't get locked into using this special version of the accounting tools. Rather, you might back out at any time and in any direction (v0 or v3 format). You might decide to completely switch over to v3 format and use multiformat-enabled acct tools only once during conversion. v3 format is source compatible with unmodified GNU acct 6.3.5, but only if v0/v1/v2 format is completely removed from the kernel (see acct cleanup patch at http://www.physik3.uni-rostock.de/tim/kernel/2.7/) and the resulting linux/include/acct.h file is copied into /usr/include/linux before ./configure is invoked. among other things. Ryan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: acct v3 support
On Fri, Sep 09, 2005 at 04:50:03PM +0200, Christoph Hellwig wrote: > On Wed, Sep 07, 2005 at 02:57:47PM -0700, Ryan Lovett wrote: > > Are there plans to have more architectures enable the newer accounting file > > format via CONFIG_BSD_PROCESS_ACCT_V3 ? I'm actually only interested in > > amd64. > > > > $ egrep 'CONFIG_BSD_PROCESS_ACCT_V3=y|linux-2.6-2.6.12/debian/arch/' \ > > linux-2.6_2.6.12-5.diff > > > > The above seems to indicate that v3 is enabled for alpha and hppa. I > > realize enabling this feature may require changes in the user space tools, > > e.g. http://www.physik3.uni-rostock.de/tim/kernel/utils/acct/ > > > > Should I file a wishlist bug? > > This breaks the accounting format, so it's a change that needs a lot > of thought. I agree, though it is curious that it is enabled on alpha and hppa. Does that imply that it works with their userspace, and thus should work on other arches too. Or does it imply that no one has noticed that it doesn't work? It seems that it should be consistently on or off for all builds that have CONFIG_BSD_PROCESS_ACCT enabled, which is all builds except sparc and some arm flavours. I'd like some feedback on if CONFIG_BSD_PROCESS_ACCT should be enabled for those builds. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: acct v3 support
On Sat, Sep 10, 2005 Horms wrote: > On Fri, Sep 09, 2005 at 04:50:03PM +0200, Christoph Hellwig wrote: > > This breaks the accounting format, so it's a change that needs a lot > > of thought. > > I agree, though it is curious that it is enabled on alpha and hppa. > Does that imply that it works with their userspace, and thus should work > on other arches too. Or does it imply that no one has noticed that it > doesn't work? Most certainly the latter. v3 format is so different that it does not work 'by accident'. So the right fix for this inconsistency is to turn CONFIG_BSD_PROCESS_ACCT_V3 off on all platforms (at least until userland is able to understand this format). Regarding transition to v3 format, I see two possible routes: 1) Install acct package with multiformat support. This allows users to switch between kernels different CONFIG_BSD_PROCESS_ACCT_V3 settings and probably smoothens the transition. 2) Don't change the acct package, but remove acct v2 format support from the kernel (and libc header files!). This way recompiling acct leads to userland tools that understand v3 format _only_. Less smooth a transition for users, but doesn't rely on my multiformat support patch being bug-free. ;-) SuSE e.g. decided to follow this route. Best would probably be to have multiformat support in an official release of GNU acct, but this requires someone to actually work on a release. So far all volunteers (including me) have stepped back from this task before they got a release out. :-( Btw., don't forget the other tools that read the accounting file. "atop" was brought to my attention, but I haven't looked into it yet. Tim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: acct v3 support
On Sat, Sep 10, 2005 at 07:21:30PM +0200, Tim Schmielau wrote: > On Sat, Sep 10, 2005 Horms wrote: > > On Fri, Sep 09, 2005 at 04:50:03PM +0200, Christoph Hellwig wrote: > > > This breaks the accounting format, so it's a change that needs a lot > > > of thought. > > > > I agree, though it is curious that it is enabled on alpha and hppa. > > Does that imply that it works with their userspace, and thus should work > > on other arches too. Or does it imply that no one has noticed that it > > doesn't work? > > Most certainly the latter. v3 format is so different that it does not work > 'by accident'. So the right fix for this inconsistency is to turn > CONFIG_BSD_PROCESS_ACCT_V3 off on all platforms (at least until userland > is able to understand this format). Thanks for the advice, I shall make that so. > Regarding transition to v3 format, I see two possible routes: > > 1) Install acct package with multiformat support. This allows users to >switch between kernels different CONFIG_BSD_PROCESS_ACCT_V3 settings >and probably smoothens the transition. > > 2) Don't change the acct package, but remove acct v2 format support from >the kernel (and libc header files!). >This way recompiling acct leads to userland tools that understand >v3 format _only_. >Less smooth a transition for users, but doesn't rely on my >multiformat support patch being bug-free. ;-) >SuSE e.g. decided to follow this route. The second option is problematic becase Debian supports custom kernels, and its probably not reasonable to mandate that custom built kernels do not have v2 support. Morover, this seems to be a substantial deviation from upstream, which is something that we would like to avoid. > Best would probably be to have multiformat support in an official release > of GNU acct, but this requires someone to actually work on a release. So > far all volunteers (including me) have stepped back from this task before > they got a release out. :-( :) > Btw., don't forget the other tools that read the accounting file. > "atop" was brought to my attention, but I haven't looked into it yet. > > Tim -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
