Date: Thu, 22 Mar 2007 09:55:35 -0400 (EDT) From: Igor Peshansky Reply-To: cygwin AT cygwin DOT com To: cygwin AT cygwin DOT com cc: neo napster Subject: Re: Sysdef Command not avaliable? In-Reply-To: Message-ID: References: <969220 DOT 97052 DOT qm AT web7606 DOT mail DOT in DOT yahoo DOT com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Thu, 22 Mar 2007, Igor Peshansky wrote: > On Thu, 22 Mar 2007, neo napster wrote: > > > In Unix, we have sysdef command to know the > > system wide defined values with sysdef command. > > > > Can I know what is similiar command in Cygwin? > > I don't know of a similar command in Cygwin. > > > Or how would I get to know system wide defined values > > in Cygwin? > > Some of these values can be found by looking through the header files, or > using other tools, like bash's ulimit builtin. If you give more specifics > on the values that you want to know, people here can give you better > pointers on where to find them. Theoretically, someone[*] can patch > cygcheck to produce a sysdef-style report, but > . > HTH, > Igor > [*] That someone could be you. . Forgot: much of the system information is also available via the /proc virtual directory tree. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu | igor AT watson DOT ibm DOT com ZZZzz /,`.-'`' -. ;-;;,_ Igor Peshansky, Ph.D. (name changed!) |,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! Freedom is just another word for "nothing left to lose"... -- Janis Joplin -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/