I've seen lots of warnings about filesystems being full. I don't remember ever seeing a directory full warning.
Please show us the EXACT warning message that you're getting when you login, output from the commands:
and output from the command:
(we only need the line from mount corresponding to the filesystem shown in the df command output).
what should i do in this situation. the system crashes and when it rebooted, it tries to dump the core files in the savecore directory. it finds that there is not enough space to dump the files so it just goes ahead and boots up and saves as much core as the directory can withhold
1.
now my... (1 Reply)
Dear experts
My / directory shows 100% full. What should I do???
What is normal size and
how can I prevent it.
I am using Solaris 8 on an Ultra 60.
Thanks for your advises.
Reza (6 Replies)
Is there a way of listing everything under a directory.
So for example if you wanted to know everything under the USR directory you would get all the sub directories and files in those directories as well as the file directly under the USR directory. I would imagine that you could do this... (5 Replies)
I'm not a unix admin, just fell into support, so I may be asking a real duh question.
Client runs a PeopleSoft HR/Payrool system. The batch server runs in HPUX PA_RISC 11.11
When a batch process runs, output is written to "staging" directory. When the job finishes, successfully or not, the... (1 Reply)
root directory in server / is full 100% , i already tried to delete any core file , log , ..
still files under /proc directory take more than 4 G..
what you advice please i don't want to format the server and install again and re partition , i tried the FORMAT tools ! but it seems i cant do... (5 Replies)
Dear All,
We are on AIX OS, /tmp directory is filled up to 99% percent,
Please suggest, How to get free space for "/tmp"?
which files can be deleted from /tmp? and How to delete it? is there any commands.....
Thanks in advance,
Its very urgent, Helpful answers will be appreciated,
Please... (7 Replies)
Hey
I'm new to the forums here, and I'm seeking help for this script that I'm writing. When I do ls -l of a directory it shows the full pathname for files in it. For example, if the directory is /internet/post/forum/ and the file is topic, it currently shows internet/post/forum/topic. What's the... (3 Replies)
I think I know what this is doing, but the 'eval' is confusing
fname=$(echo ${lineItem} | awk 'BEGIN {FS=";"}{print $1}')
fname=${fname%%+(])}
fname=${fname##+(])}
eval "fname=${fname}"
The first line extracts the contents of the line preceeding the ";"
2nd & 3rd lines trim the value (I... (5 Replies)
My input is as below :
/splunk/scrubbed/rebate/IFIND.REBTE.WROC.txt
/splunk/scrubbed/rebate/IFIND.REBTE.WROC.txt
/splunk/scrubbed/loyal/IFIND.HELLO.WROC.txt
/splunk/scrubbed/triumph/ifind.triumph.txt
From the above input I want to extract the file names only .
Basically I want to... (5 Replies)
Discussion started by: IshuGupta
5 Replies
LEARN ABOUT DEBIAN
gnome2::vfs::directory::handle
Gnome2::VFS::Directory::Handle(3pm) User Contributed Perl Documentation Gnome2::VFS::Directory::Handle(3pm)NAME
Gnome2::VFS::Directory::Handle - respresents a directory
METHODS
result = $handle->close
list = $handle->read_next
Returns a GnomeVFSResult and a GnomeVFSFileInfo.
ENUMS AND FLAGS
enum Gnome2::VFS::Result
o 'ok' / 'GNOME_VFS_OK'
o 'error-not-found' / 'GNOME_VFS_ERROR_NOT_FOUND'
o 'error-generic' / 'GNOME_VFS_ERROR_GENERIC'
o 'error-internal' / 'GNOME_VFS_ERROR_INTERNAL'
o 'error-bad-parameters' / 'GNOME_VFS_ERROR_BAD_PARAMETERS'
o 'error-not-supported' / 'GNOME_VFS_ERROR_NOT_SUPPORTED'
o 'error-io' / 'GNOME_VFS_ERROR_IO'
o 'error-corrupted-data' / 'GNOME_VFS_ERROR_CORRUPTED_DATA'
o 'error-wrong-format' / 'GNOME_VFS_ERROR_WRONG_FORMAT'
o 'error-bad-file' / 'GNOME_VFS_ERROR_BAD_FILE'
o 'error-too-big' / 'GNOME_VFS_ERROR_TOO_BIG'
o 'error-no-space' / 'GNOME_VFS_ERROR_NO_SPACE'
o 'error-read-only' / 'GNOME_VFS_ERROR_READ_ONLY'
o 'error-invalid-uri' / 'GNOME_VFS_ERROR_INVALID_URI'
o 'error-not-open' / 'GNOME_VFS_ERROR_NOT_OPEN'
o 'error-invalid-open-mode' / 'GNOME_VFS_ERROR_INVALID_OPEN_MODE'
o 'error-access-denied' / 'GNOME_VFS_ERROR_ACCESS_DENIED'
o 'error-too-many-open-files' / 'GNOME_VFS_ERROR_TOO_MANY_OPEN_FILES'
o 'error-eof' / 'GNOME_VFS_ERROR_EOF'
o 'error-not-a-directory' / 'GNOME_VFS_ERROR_NOT_A_DIRECTORY'
o 'error-in-progress' / 'GNOME_VFS_ERROR_IN_PROGRESS'
o 'error-interrupted' / 'GNOME_VFS_ERROR_INTERRUPTED'
o 'error-file-exists' / 'GNOME_VFS_ERROR_FILE_EXISTS'
o 'error-loop' / 'GNOME_VFS_ERROR_LOOP'
o 'error-not-permitted' / 'GNOME_VFS_ERROR_NOT_PERMITTED'
o 'error-is-directory' / 'GNOME_VFS_ERROR_IS_DIRECTORY'
o 'error-no-memory' / 'GNOME_VFS_ERROR_NO_MEMORY'
o 'error-host-not-found' / 'GNOME_VFS_ERROR_HOST_NOT_FOUND'
o 'error-invalid-host-name' / 'GNOME_VFS_ERROR_INVALID_HOST_NAME'
o 'error-host-has-no-address' / 'GNOME_VFS_ERROR_HOST_HAS_NO_ADDRESS'
o 'error-login-failed' / 'GNOME_VFS_ERROR_LOGIN_FAILED'
o 'error-cancelled' / 'GNOME_VFS_ERROR_CANCELLED'
o 'error-directory-busy' / 'GNOME_VFS_ERROR_DIRECTORY_BUSY'
o 'error-directory-not-empty' / 'GNOME_VFS_ERROR_DIRECTORY_NOT_EMPTY'
o 'error-too-many-links' / 'GNOME_VFS_ERROR_TOO_MANY_LINKS'
o 'error-read-only-file-system' / 'GNOME_VFS_ERROR_READ_ONLY_FILE_SYSTEM'
o 'error-not-same-file-system' / 'GNOME_VFS_ERROR_NOT_SAME_FILE_SYSTEM'
o 'error-name-too-long' / 'GNOME_VFS_ERROR_NAME_TOO_LONG'
o 'error-service-not-available' / 'GNOME_VFS_ERROR_SERVICE_NOT_AVAILABLE'
o 'error-service-obsolete' / 'GNOME_VFS_ERROR_SERVICE_OBSOLETE'
o 'error-protocol-error' / 'GNOME_VFS_ERROR_PROTOCOL_ERROR'
o 'error-no-master-browser' / 'GNOME_VFS_ERROR_NO_MASTER_BROWSER'
o 'error-no-default' / 'GNOME_VFS_ERROR_NO_DEFAULT'
o 'error-no-handler' / 'GNOME_VFS_ERROR_NO_HANDLER'
o 'error-parse' / 'GNOME_VFS_ERROR_PARSE'
o 'error-launch' / 'GNOME_VFS_ERROR_LAUNCH'
o 'error-timeout' / 'GNOME_VFS_ERROR_TIMEOUT'
o 'error-nameserver' / 'GNOME_VFS_ERROR_NAMESERVER'
o 'error-locked' / 'GNOME_VFS_ERROR_LOCKED'
o 'error-deprecated-function' / 'GNOME_VFS_ERROR_DEPRECATED_FUNCTION'
o 'error-invalid-filename' / 'GNOME_VFS_ERROR_INVALID_FILENAME'
o 'error-not-a-symbolic-link' / 'GNOME_VFS_ERROR_NOT_A_SYMBOLIC_LINK'
o 'num-errors' / 'GNOME_VFS_NUM_ERRORS'
SEE ALSO
Gnome2::VFS
COPYRIGHT
Copyright (C) 2003-2007 by the gtk2-perl team.
This software is licensed under the LGPL. See Gnome2::VFS for a full notice.
perl v5.14.2 2011-11-15 Gnome2::VFS::Directory::Handle(3pm)