8.10 ResultError Codes

8.10 Result/Error Codes

All of the GnomeVFSResult values in this section are greater than or equal to 0 and smaller than GNOME_VFS_NUM_ERRORS :

  • GNOME_VFS_OK : Operation successful.

  • GNOME_VFS_ERROR_NOT_FOUND : File or directory does not exist.

  • GNOME_VFS_ERROR_GENERIC : Unknown/ undefined error.

  • GNOME_VFS_ERROR_INTERNAL : Internal error; probably a bug in GnomeVFS.

  • GNOME_VFS_ERROR_BAD_PARAMETERS : Invalid function parameters, such as NULL instead of a URI string.

  • GNOME_VFS_ERROR_NOT_SUPPORTED : Operation or access mode not supported.

  • GNOME_VFS_ERROR_IO : Error when reading or writing.

  • GNOME_VFS_ERROR_CORRUPTED_DATA : Invalid data in the file system source (such as an archive).

  • GNOME_VFS_ERROR_WRONG_FORMAT : File system source does not match the access method.

  • GNOME_VFS_ERROR_BAD_FILE : Invalid file descriptor.

  • GNOME_VFS_ERROR_TOO_BIG : File too large (to read, write, or manipulate).

  • GNOME_VFS_ERROR_NO_SPACE : Target file system is out of free space.

  • GNOME_VFS_ERROR_READ_ONLY : Target file system is read-only space.


  • GNOME_VFS_ERROR_NOT_OPEN : Tried to access file data with a closed descriptor.

  • GNOME_VFS_ERROR_INVALID_OPEN_MODE : Invalid GnomeVFSOpenMode parameter when opening a file.

  • GNOME_VFS_ERROR_ACCESS_DENIED : Permission denied .

  • GNOME_VFS_ERROR_TOO_MANY_OPEN_FILES : Process cannot open any more open file descriptors.

  • GNOME_VFS_ERROR_EOF : Attempt to access past the end of a file.

  • GNOME_VFS_ERROR_NOT_A_DIRECTORY : Attempt to access a regular file as a directory.

  • GNOME_VFS_ERROR_IN_PROGRESS : Operation failed because another operation is pending.

  • GNOME_VFS_ERROR_INTERRUPTED : Something stopped the file access.

  • GNOME_VFS_ERROR_FILE_EXISTS : Attempt to create a file that already exists.

  • GNOME_VFS_ERROR_LOOP : Infinite symbolic link loop detected .

  • GNOME_VFS_ERROR_NOT_PERMITTED : Operation not allowed (for example, a URI with "unsafe" characters was specified).

  • GNOME_VFS_ERROR_IS_DIRECTORY : Attempt to access a directory as a regular file.

  • GNOME_VFS_ERROR_NO_MEMORY : GnomeVFS has run out of memory.

  • GNOME_VFS_ERROR_HOST_NOT_FOUND : Host in URI not found.

  • GNOME_VFS_ERROR_INVALID_HOST_NAME : Invalid hostname in URI.

  • GNOME_VFS_ERROR_HOST_HAS_NO_ADDRESS : Could not determine the address from the URI hostname.

  • GNOME_VFS_ERROR_LOGIN_FAILED : Username or password invalid.

  • GNOME_VFS_ERROR_CANCELLED : User interrupted the operation.

  • GNOME_VFS_ERROR_DIRECTORY_BUSY : Attempt to access a directory that has a read lock.

  • GNOME_VFS_ERROR_DIRECTORY_NOT_EMPTY : Attempt to remove a directory that is not empty.

  • GNOME_VFS_ERROR_TOO_MANY_LINKS : Attempt to create too many hard links to a single inode.

  • GNOME_VFS_ERROR_READ_ONLY_FILE_SYSTEM : Attempt to write to a read-only file system.

  • GNOME_VFS_ERROR_NOT_SAME_FILE_SYSTEM : Attempt to perform an operation that requires its items to be on the same file system, using items on different file systems.

  • GNOME_VFS_ERROR_NAME_TOO_LONG : Filename too long.

  • GNOME_VFS_ERROR_SERVICE_NOT_AVAILABLE : Requested service is not available (perhaps not implemented).

  • GNOME_VFS_ERROR_SERVICE_OBSOLETE : Requested service is obsolete and unusable.


To get a string corresponding to an error code, call

 gnome_vfs_result_to_string(  result_code  ) 

Do not attempt to deallocate or alter this string. You can place the function call directly inside g_printerr() . If you want to manipulate the error message, make a copy with g_strdup() .

The Official GNOME 2 Developers Guide
The Official GNOME 2 Developers Guide
ISBN: 1593270305
EAN: 2147483647
Year: 2004
Pages: 108

Similar book on Amazon

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net