From nicolas.niclausse@REDACTED  Fri Feb 13 15:34:30 2004
From: nicolas.niclausse@REDACTED (Nicolas Niclausse)
Date: Fri, 13 Feb 2004 15:34:30 +0100
Subject: patch for get_memory_usage_linux on linux-2.6
Message-ID: <87isibjbex.fsf@schultze.ird.idealx.com>

Hello,

Since /proc/meminfo has changed in linux 2.6, the os_mon application do
not work anymore. The following patch fix the parsing of /proc/meminfo
on a linux 2.6 kernel


Btw, the fonction gives the memory used on a linux system, but since
linux is using all the available memory for caching (and buffering), the
free memory reported by this function is meaningless. Maybe we should
subtract the cache size to the MemUsed value ?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: mem_linux-2.6.patch
Type: text/x-patch
Size: 1084 bytes
Desc: patch
URL: <http://erlang.org/pipermail/erlang-patches/attachments/20040213/297c2a42/attachment.bin>
-------------- next part --------------

-- 
Nicolas NICLAUSSE                       IDEALX S.A.S.
T?l:01 44 42 00 00                      http://IDEALX.com/

From vances@REDACTED  Sat Feb 14 21:42:02 2004
From: vances@REDACTED (Vance Shipley)
Date: Sat, 14 Feb 2004 15:42:02 -0500
Subject: i:iaa/1 documentation error
Message-ID: <20040214204202.GC14852@frogman.motivity.ca>


The function i:iaa/1 is documented incorrectly with respect to
how it handles a single flag.

	-Vance


- iaa(Flag) -> true
-      Types:
-           Flag = FlagItem | [FlagItem]
-           FlagItem = init | break | exit | false

+ iaa(Flags) -> true
+      Types:
+           Flags = [init | break | exit | false]



From vances@REDACTED  Sun Feb 15 08:31:10 2004
From: vances@REDACTED (Vance Shipley)
Date: Sun, 15 Feb 2004 02:31:10 -0500
Subject: et documentation error
Message-ID: <20040215073110.GB16053@frogman.motivity.ca>


In the et module documentation the constraints on X
should be between 0 and 100.

- DetailLevel = integer(X) when X =< 0, X >= 100
+ DetailLevel = integer(X) when X >= 0, X =< 100

	-Vance



From klacke@REDACTED  Sat Feb 28 17:23:01 2004
From: klacke@REDACTED (klacke@REDACTED)
Date: Sat, 28 Feb 2004 17:23:01 +0100
Subject: error_logger_file_h
Message-ID: <20040228162301.GA19040@hyber.org>

Howdy,

I think that when doing error_logger:logfile(FileName)
the file FileName shouldn't be truncated as it is now.
In principle it makes it impossible to use the function
across restarts. 

I suggest:


diff -c -r1.1.1.3 error_logger_file_h.erl
*** error_logger_file_h.erl     25 Feb 2003 08:27:23 -0000      1.1.1.3
--- error_logger_file_h.erl     28 Feb 2004 16:05:53 -0000
***************
*** 49,55 ****
  
  init(File, PrevHandler) ->
      process_flag(trap_exit, true),
!     case file:open(File, write) of
        {ok,Fd} ->
            {ok, {Fd, File, PrevHandler}};
        Error ->
--- 49,55 ----
  
  init(File, PrevHandler) ->
      process_flag(trap_exit, true),
!     case file:open(File, append) of
        {ok,Fd} ->
            {ok, {Fd, File, PrevHandler}};
        Error ->




This shouldn't break any code, and is also more intuitive.




/klacke



-- 
Claes Wikstrom                        -- Caps lock is nowhere and
http://www.hyber.org                  -- everything is under control