Sponsored Content
Top Forums Programming New to C Programming in UNIX environment Post 302080484 by blowtorch on Wednesday 19th of July 2006 05:51:28 AM
Old 07-19-2006
What OS are you working on? That may tell you what native C compiler you've used. Also, check the output for 'ls -l `which cc`'. (Note the backquotes around 'which'). You may find that cc is actually a link to gcc (quite common). As for the documentation, is it for learning C or learning how to use cc/gcc? For C and debugging links, check the Unix Tutorials/Programming Tutorials/Shell Scripting Tutorials page.

In fact, I think that should answer almost all your questions. And one more piece of advice... check the FAQs page. You will get tutorials, recommended pages, ready-made scripts and more.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

MixWindows UNIX environment

I was wondering if anyone has had any experience in this area. The company that I work at is trying to bring a Windows 2000 server online and have the UNIX workstations and Clients connect to it like it is anothe UNIX box. They have been using Windows Services for UNIX to do this but are having... (1 Reply)
Discussion started by: kaikara1
1 Replies

2. Post Here to Contact Site Administrators and Moderators

Java Programming in UNIX Environment

A suggetion: Don't we need to start Java Programming in UNIX Environment Forum ? (1 Reply)
Discussion started by: cub
1 Replies

3. Programming

c programming or unix programming!?

i would like advice on the usbject of c programming (in the middle of reading a book on C). could i benefit more if i apply that knowledge in the unix format if i were able to, or would that take the point out of learning C, basically I want to stay away from strying too far away from unix and use... (1 Reply)
Discussion started by: moxxx68
1 Replies

4. Shell Programming and Scripting

programming for unix environment

i have to make a menu based program to allow iusers to select the system information about their machine that they want. All i have been taught is how to enter commands at the command prompt like simple commands such as pwd and cd directory to change directory (not even sure if that is right). But... (1 Reply)
Discussion started by: carlvernon
1 Replies

5. Shell Programming and Scripting

Unix Systems Programming Vs Unix Programming

Several months ago I found a link that explained the difference between how a Unix Systems Admin would do scripting compared to what a Unix Programmer would do. It showed a basic script and then show several iterations that explained how the Systems Admin would change it to make it better. I was... (0 Replies)
Discussion started by: BCarlson
0 Replies

6. UNIX for Dummies Questions & Answers

unix environment

Hi, Can anyone recommend a site where one can practise UNIX scripting . I don't have UNIX on my machine however I have heard there are some sites which let you log on to their servers for free. Thanks Rohit (2 Replies)
Discussion started by: rohitv
2 Replies

7. UNIX for Dummies Questions & Answers

Carreer:Networking Programming in Unix (C programming Language)

Hello, I am trying to learn Networking Programming in C in unix enviorment. I want to know how good it is to become a network programmer. i am crazy about Network programming but i also want to opt for the best carreer options. Anybody experienced Network Programmer, please tell me is my... (5 Replies)
Discussion started by: vibhory2j
5 Replies

8. UNIX for Dummies Questions & Answers

How does unix system administration, unix programming, unix network programming differ?

How does unix system administration, unix programming, unix network programming differ? Please help. (0 Replies)
Discussion started by: thulasidharan2k
0 Replies

9. Shell Programming and Scripting

Grep problem from The Unix Programming Environment

Hi Here is the problem ( Exercise 3-3, Using The Shell of The Unix Programming Environment, Kerninghan, Pike, 3rd edition ): Predict what each of the following grep commands will do, and then verify your understanding. grep \$ grep \\$ grep \\\$ grep '\$' grep '\'$' grep \\ grep \\\\... (3 Replies)
Discussion started by: dum_dum20
3 Replies
ulimit(1)						      General Commands Manual							 ulimit(1)

NAME
ulimit - Sets or reports a resource limit SYNOPSIS
ulimit [-HSacdfmnstvw] [limit] STANDARDS
Interfaces documented on this reference page conform to industry standards as follows: ulimit: XCU5.0, XBD5.0 Refer to the standards(5) reference page for more information about industry standards and associated tags. OPTIONS
[Tru64 UNIX] The limits specified for the resources are hard limits. A hard limit cannot be increased once it is set. [Tru64 UNIX] The limits specified for the resources are soft limits. A soft limit can be increased up to the value of the hard limit. [Tru64 UNIX] Lists all of the current resource limits. The limit operand is not permitted with this option. [Tru64 UNIX] The limit operand specifies the number of 512-byte blocks for core dumps. [Tru64 UNIX] The limit operand specifies the number of Kilobytes for the data area. The limit operand specifies the number of 512-byte blocks for files written by child processes (files of any size can be read). [Tru64 UNIX] The limit operand specifies the number of Kilobytes for the size of physical memory. [Tru64 UNIX] The limit operand specifies the number of file descriptors. [Tru64 UNIX] The limit operand specifies the number of Kilobytes for the stack area. [Tru64 UNIX] The limit op- erand specifies the number of seconds to be used by each process. [Tru64 UNIX] The limit operand specifies the number of Kilobytes for virtual memory. This option is supported only if RLIMIT_VMEM has been defined in /usr/include/sys/resource.h at compile-time. [Tru64 UNIX] The limit operand specifies the number of Kilobytes for the swap area. This option is supported only if RLIMIT_SWAP has been defined in /usr/include/sys/resource.h at compile-time. OPERANDS
If no options are specified, this is the number of 512 byte blocks to use as the new limit to file size. Otherwise, it is the limit applied to the resource indicatd by the option. [Tru64 UNIX] This operand is not allowed with the -a option. If this operand is omitted, the current limit for the indicated resource is reported. DESCRIPTION
This command sets, or reports, the limit on the size of system resources, as indicated by the option. [Tru64 UNIX] If neither the -H option nor the -S option is specified, the limit applies to both hard and soft limits. If only the -a option is specified, soft limits are reported. If there is no limit on a resource, the limit is reported as unlimited. NOTES
The ulimit command affects only the current execution environment, therefore it has no effect when run in a separate execution environment such as one of the following: nohup ulimit -f 10000 env ulimit 10000 RESTRICTIONS
Once a limit has been decreased, only a user with superuser privileges may increase it, even back to its original value. EXIT STATUS
The following exit values are returned: Successful completion. A request for a higher limit was rejected or an error occurred. EXAMPLES
To set the file size limit to 51,200 bytes, enter: ulimit -f 100 To report the current file size limit, enter: ulimit The following example displays all current resource limits: % ulimit -a time(seconds) unlimited file(blocks) unlimited data(kbytes) 131072 stack(kbytes) 2048 memory(kbytes) 84280 coredump(blocks) unlimited nofiles(descriptors) 4096 vmemory(kbytes) 1048576 ENVIRONMENT VARIABLES
The following environment variables affect the execution of ulimit: Provides a default value for the internationalization variables that are unset or null. If LANG is unset or null, the corresponding value from the default locale is used. If any of the internationalization variables contain an invalid setting, the utility behaves as if none of the variables had been defined. If set to a non-empty string value, overrides the values of all the other internationalization variables. Determines the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as opposed to multibyte characters in arguments). Determines the locale for the format and contents of diagnostic messages written to standard error. Determines the location of message catalogues for the processing of LC_MESSAGES. SEE ALSO
Routines: ulimit(3) Standards: standards(5) ulimit(1)
All times are GMT -4. The time now is 01:06 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy