We run our Ubuntu systems with a default umask of 0066, which is pretty common in a university setting. Generally everyone is in a common Unix group. This prevents everyone from being able to write to each other's files by default.
Unfortunately, this seems to cause problems with the communication between makerware and conveyor. Whenever we print preview, the apparent plan is to print nothing. When we actually print, the Replicator 2 just puts down a strip of "preprint" filament and stops.
We are forced to launch it
umask 0022
makerware
so files that makerware creates in /tmp are readable by conveyor. This works for now. It's not really optimal since people may save a .thing file they want to keep private.
It would be nice if makerware and conveyor were not so sensitive to the default umask of the system. A couple of ideas: makerware could chmod the files appropriately, there could be a /var/spool/conveyor directory which is chmod g+s that users in a certain group can write to, or something different.
We run our Ubuntu systems with a default umask of
0066, which is pretty common in a university setting. Generally everyone is in a common Unix group. This prevents everyone from being able to write to each other's files by default.Unfortunately, this seems to cause problems with the communication between makerware and conveyor. Whenever we print preview, the apparent plan is to print nothing. When we actually print, the Replicator 2 just puts down a strip of "preprint" filament and stops.
We are forced to launch it
so files that makerware creates in
/tmpare readable by conveyor. This works for now. It's not really optimal since people may save a.thingfile they want to keep private.It would be nice if makerware and conveyor were not so sensitive to the default umask of the system. A couple of ideas: makerware could chmod the files appropriately, there could be a
/var/spool/conveyordirectory which ischmod g+sthat users in a certain group can write to, or something different.