[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ast-users
Subject:    Re: [ast-users] ksh93: possible bug in `read' builtin?
From:       Glenn Fowler <gsf () research ! att ! com>
Date:       2011-12-06 20:23:00
Message-ID: 201112062023.pB6KN0i1012068 () penguin ! research ! att ! com
[Download RAW message or body]


thanks for the feedback on the topic of sfgetr() line limits

its was a few years ago when we saw bad behavior on one of our systems
at this point I don't recall which one it was

unix already has mechanisms to handle resource hogs:
ulimit(2), setrlimit(2) and the ulimit(1) shell builtin

if we remove the line limit then sfgetr() on a big enough line
will get an sbrk() or mmap() error when trying to grow the line buffer
and that error will make its way to a diagnostic at the command level

ulimit -M (unlimited by default) can be used to limit the
memory allocations in a process, including memory used by sfgetr()

_______________________________________________
ast-users mailing list
ast-users@research.att.com
https://mailman.research.att.com/mailman/listinfo/ast-users
[prev in list] [next in list] [prev in thread] [next in thread]