Others feel free to chime in..
First and foremost, these errors are an indication something
is very wrong, regardless of maya or scene files.
> rushd: WARNING: chdir(/var/tmp/.RUSH_TMP.190): Permission denied
> [..]
> Error: default temp directory /usr/tmp does not have write permissions.
> *** Fatal Error: Failed creating directory: /usr/tmp
Correct those, and the maya scene file issues will likely
go away as well.
Some are messages from rush, some are from maya. Both indicate
perm problems with /var/tmp. (often /usr/tmp and /var/tmp are
the same dir; the former being a link to the latter)
There are at least two things that have been added to linux
(and OSX) over the years that affect the way permissions
are handled: acl's and selinux (see 'man acl' and 'man selinux')
So you'll want to check those.
Also, traditional unix perms can create this situation as well
(eg. someone enabling an improper sticky bit on eg. the /var/tmp dir)
You mentioned you disabled selinux; though I don't right away
suspect that given the above, what technique did you use?
Did you disable it in grub, or /etc/sysconfig/selinux, or both?
Try checking your work to make sure it's off:
selinuxenabled; echo $?
From the selinuxenabled(8) man page:
>> It exits with status 0 if SELinux is enabled and 1 if it is not enabled.
..so if the above prints 0, it's still on.
Try this test: ssh into host 'bing' as 'root' and run:
mkdir -m 777 /var/tmp/my-test # create a dir with wide open perms
su - dbrowne # become the dbrowne user
cd /var/tmp/my-test # see if you can cd into the dir
Then try (again, as root first):
mkdir -m 755 /var/tmp/my-test2 # create a dir with perms mostly for user
chown dbrowne.dbrowne /var/tmp/my-test2 # change ownership
su - dbrowne # become the dbrowne user
cd /var/tmp/my-test2 # see if you can cd into the dir
Does the cd operation fail?
Check the perms + acls on /, /var, and /var/tmp against a working machine
of the same type to see if there's anything wrong with the perm settings.
Look in particular for unusual 't' or 's' flags in the perms.
A messed up /var/tmp could affect /all/ programs badly including maya, rush, etc.
Checking on my FC14 system, I get:
$ ls -ladZ / /var /var/tmp
dr-xr-xr-x. root root system_u:object_r:root_t:s0 /
drwxr-xr-x. root root system_u:object_r:var_t:s0 /var
drwxrwxrwt. root root system_u:object_r:tmp_t:s0 /var/tmp
^^^^^^^^^
$ getfacl -a /var/tmp
getfacl: Removing leading '/' from absolute path names
# file: var/tmp
# owner: root
# group: root
# flags: --t
user::rwx
group::rwx
other::rwx
Also: is this a freshly set up box that you installed yourself,
or is it a 'pre-installed' system that is perhaps been customized
by someone else? If the latter, you might consider reinstalling
the OS yourself if you suspect it may have been customized.
--
Greg Ercolano, erco@(email surpressed)
Seriss Corporation
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)ext.23
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)
|