Sponsored Content
Full Discussion: max. size of file
Operating Systems Solaris max. size of file Post 302122338 by suresh_chinwin on Wednesday 20th of June 2007 05:51:54 AM
Old 06-20-2007
max file size in unix

The max file size in unix is determined by the ulimit option. The ulimit stands for user limit which specifies the largest file that can be created by the user.

$ulimit

2097152

means that the max size of a file that can be created is 2097152 bytes or 2048 KB.

We can also reset the ulimit value

$ulimit=1 specifies that the user limit is now 512 bytes(1 refers to 512 block) and is only active for this session.

A normal user can decrease the ulimit value but only the superuser(root) has the permissions to increase this value.

Hope this clears your doubt. Thank you.

Suresh.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

setting max log file size...

Hello all! I have found a new home, this place is great! I have been searching for days to find a way to set a max size for a log.txt file using a cron job exicuting a shell script. Is it possible for a script to remove older entries in a log file to maintain a limited file size? If so,... (5 Replies)
Discussion started by: v-rod
5 Replies

2. Shell Programming and Scripting

Max size of variable

What is the maximum amount of characters that you can have in a varible name in the ksh shell? (1 Reply)
Discussion started by: lesstjm
1 Replies

3. UNIX for Dummies Questions & Answers

Max I/O Size

My HP-UX 11.0 system is supporting an Oracle database. I have found a number of references on the Net to the "Max I/O size" in relation to setting Oracle parameters. How can I tell what my max i/o size is? I originally made the assumption that it was referring to my stripe size but now I think... (1 Reply)
Discussion started by: keelba
1 Replies

4. Programming

Max file size can't exceed 2 GB

We have Sun OS 5.9 we are doing a backup process (ProC program) that uses the function... fprintf(fp,"%s;%s;%s;%s;%s;%ld;%ld;%ld;%ld;%s;%s;%s;%d;%s;%s;%s;%ld;%s;%s;%s;%ld;%ld;%s;%ld;%s;%ld;%s;%s;%c%c",x_contrno, x_subno, x_b_subno,x_transdate,x_last_traffic_date,BillAmt_s, x_billamount_int,... (10 Replies)
Discussion started by: atiato
10 Replies

5. UNIX for Advanced & Expert Users

How to determine the max file size

Does anyone know a way to determine the maximum filesize on a file system on Solaris, HP-UX, AIX, Linux, and OSF1 using the command line? TIA (2 Replies)
Discussion started by: dknight
2 Replies

6. UNIX for Advanced & Expert Users

Max. file size

i want to know what is the maximum file size supported by linux with ext3 file system. (1 Reply)
Discussion started by: nagalenoj
1 Replies

7. UNIX for Dummies Questions & Answers

MAX file size limited to 2GB

Hi All, We are running HP rp7400 box with hpux 11iv1. Recently, we changed 3 kernel parameters a) msgseg from 32560 to 32767 b) msgmnb from 65536 to 65535 c) msgssz from 128 to 256 Then we noticed that all application debug file size increase upto 2GB then it stops. So far we did not... (1 Reply)
Discussion started by: mhbd
1 Replies

8. UNIX for Advanced & Expert Users

Max size of the attachment

Hi Gurus, I am unable to send a file which size is more than 10mb through the "sendmail" command in unix. I searched from internet and followed the path specified over there "/etc/mail/sendmail.cf" and too "/etc/mail/main.cf" but found in those files below lines. # maximum message size... (1 Reply)
Discussion started by: sanjay.login
1 Replies

9. UNIX for Dummies Questions & Answers

Restrict Max file size

Hello All, I am working on an issue, where I need to check the max file size of a file. If the file size exceeds 2 GB, then I need to generate an error message. Since the file system does not allow a file to be created larger than 2 GB, I am planning to use named pipes & AWK file to acheive my... (6 Replies)
Discussion started by: puru2121
6 Replies

10. Solaris

Clamd max file size Solaris 10

Hi, I've compiled a 64-bit version of ClamAV 0.98.7 on my Solaris 10 SPARC server. I have a selection of files all containing the eicar signature but clamd is only picking up the signature in the files <2GB. I have the following set in clamd.conf, to remove file size checking: MaxScanSize 0... (4 Replies)
Discussion started by: Troutfest
4 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 11:11 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy