03-18-2007
You don't need to be fancy or use non-standard commands to have a problem. Scripts can run fine for a long time and then encounter data they can't handle well. As one example, if you ftp a file to /tmp and the file is unexpectedly large it would result in this exact problem.
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
Dear Experts,
We are using Digital Unix 4.0d on Alpha DS-20 E.
/var/adm/messages showed the following error
Jul 24 19:58:37 cbehotbill2 vmunix: /BSCSprod: write failed, file system is full
Jul 24 19:58:38 cbehotbill2 last message repeated 2 times
But df -k showed
BSCS_dmn#BSCSprod ... (4 Replies)
Discussion started by: geraldwilson
4 Replies
2. Programming
When i run my C program which dynamically creates the output file, the program stops after sometime and gives the error "File size limit exceeded" even though my working directory has space.Can anyone plz help me out. (13 Replies)
Discussion started by: drshah
13 Replies
3. Solaris
Hi Guys
I need to increase the size of my /tmp swap file. What is the easiest way to do this.
Thanks
Carson (2 Replies)
Discussion started by: cmackin
2 Replies
4. UNIX for Dummies Questions & Answers
Hello -
O/S is UnixWare 7.1.4
My prefered method of copying files between servers is 'rcp', which does not recognize symbolic links; therefore, files are duplicated many times over.
To avoid this duplication, I would like to use 'tar' and/or 'cpio' and pipe them through 'rcp', but... (1 Reply)
Discussion started by: rm -r *
1 Replies
5. Solaris
hi every one ,
i know how to add swap space in ufs file system.
but i m facing problem in veritas file system .
i wants to know how will i create swap or add new swap space in existing swap space .
Note: disk under veritas volume manager control .
please help me to solve this issue . (5 Replies)
Discussion started by: samy123
5 Replies
6. AIX
Hi,
I would like to know if /tmp file system is full, wheather it will affect the peformance of application installed on AIX. if Memory and CPU are not heavily utilized.
Regards,
Manoj. (1 Reply)
Discussion started by: manoj.solaris
1 Replies
7. Solaris
Hello all,
The issue is
# df -h /tmp
Filesystem size used avail capacity Mounted on
swap 4.0G 4.0G 8.7M 100% /tmp
# du -sh /tmp/
87M /tmp
By now you probably will say that this is open file destriptor issue.
Well no, nothing... (2 Replies)
Discussion started by: click
2 Replies
8. Solaris
hi all
I am having a t5240 server in that zone is there in /var/adm/messages i am getting the following warning
WARNING: /zoneroot/zonename-zone/root/tmp: File system full, swap
space limit exceeded
if a swap is getting full what can i do.
Please use code tags next time for your... (2 Replies)
Discussion started by: nikhil kasar
2 Replies
9. Solaris
Does anyone have any advise on trying to clean up a full filesystem? I can't rm any files because of the follow:
not removed: No space left on device
Any help would be very much appreciated. (10 Replies)
Discussion started by: craigsky
10 Replies
10. Emergency UNIX and Linux Support
Hello,
This is RHEL 5.7. swap is almost full, but I am not sure, what to release and how to release space. This is production server so I would like to try all possible options before reboot.
# top
top - 00:18:26 up 327 days, 7:01, 3 users, load average: 0.16, 0.21, 0.18
Tasks: 782 total, ... (7 Replies)
Discussion started by: solaris_1977
7 Replies
LEARN ABOUT CENTOS
perl::critic::policy::inputoutput::requirebriefopen
Perl::Critic::Policy::InputOutput::RequireBriefOpen(3) User Contributed Perl Documentation Perl::Critic::Policy::InputOutput::RequireBriefOpen(3)
NAME
Perl::Critic::Policy::InputOutput::RequireBriefOpen - Close filehandles as soon as possible after opening them.
AFFILIATION
This Policy is part of the core Perl::Critic distribution.
DESCRIPTION
One way that production systems fail unexpectedly is by running out of filehandles. Filehandles are a finite resource on every operating
system that I'm aware of, and running out of them is virtually impossible to recover from. The solution is to not run out in the first
place. What causes programs to run out of filehandles? Usually, it's leaks: you open a filehandle and forget to close it, or just wait a
really long time before closing it.
This problem is rarely exposed by test systems, because the tests rarely run long enough or have enough load to hit the filehandle limit.
So, the best way to avoid the problem is 1) always close all filehandles that you open and 2) close them as soon as is practical.
This policy takes note of calls to "open()" where there is no matching "close()" call within "N" lines of code. If you really need to do a
lot of processing on an open filehandle, then you can move that processing to another method like this:
sub process_data_file {
my ($self, $filename) = @_;
open my $fh, '<', $filename
or croak 'Failed to read datafile ' . $filename . '; ' . $OS_ERROR;
$self->_parse_input_data($fh);
close $fh;
return;
}
sub _parse_input_data {
my ($self, $fh) = @_;
while (my $line = <$fh>) {
...
}
return;
}
As a special case, this policy also allows code to return the filehandle after the "open" instead of closing it. Just like the close,
however, that "return" has to be within the right number of lines. From there, you're on your own to figure out whether the code is
promptly closing the filehandle.
The STDIN, STDOUT, and STDERR handles are exempt from this policy.
CONFIGURATION
This policy allows "close()" invocations to be up to "N" lines after their corresponding "open()" calls, where "N" defaults to 9. You can
override this to set it to a different number with the "lines" setting. To do this, put entries in a .perlcriticrc file like this:
[InputOutput::RequireBriefOpen]
lines = 5
CAVEATS
"IO::File->new"
This policy only looks for explicit "open" calls. It does not detect calls to "CORE::open" or "IO::File->new" or the like.
Is it the right lexical?
We don't currently check for redeclared filehandles. So the following code is false negative, for example, because the outer scoped
filehandle is not closed:
open my $fh, '<', $file1 or croak;
if (open my $fh, '<', $file2) {
print <$fh>;
close $fh;
}
This is a contrived example, but it isn't uncommon for people to use $fh for the name of the filehandle every time. Perhaps it's time to
think of better variable names...
CREDITS
Initial development of this policy was supported by a grant from the Perl Foundation.
AUTHOR
Chris Dolan <cdolan@cpan.org>
COPYRIGHT
Copyright (c) 2007-2011 Chris Dolan. Many rights reserved.
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. The full text of this license
can be found in the LICENSE file included with this module
perl v5.16.3 2014-06-09 Perl::Critic::Policy::InputOutput::RequireBriefOpen(3)