Please do NOT change files and directories to 777 to solve 'permission denied' issues. It is the single most common sysadmin error reported by security auditors. 777 makes the file executable which can cause all sorts of problems, and also makes the file available to be DESTROYED by anyone in the system. The permission settings are there to prevent such destruction.
root should NOT be creating files for users. A normal user should create the file with umask set to 002 or 007. For 002, your file will be created with 664 (read/write by owner and group, read by anyone else) or 660 (read/write by owner and group, no one else can look at the file. The user may need to change the group ownership if the user's default is not the desired group
Now group=none is strange. I would start by creating a specific group based on the use of these files, perhaps acctg or finance or project1, whatever. Then add the various users to that group. To be sure that users have the right settings, login as the user and type the command: id That will report on the user ID and all group IDs.
Now as to a location, / (the root dirfectory) is the WORST possible location. This directory is critical to operation of the systemj and if you have a 777 file, then anyone can dump whatever they want into that file, fill the / filesystem and disable almost everything. And IMMEDIATELY change / back to 755 with owner root:root. If you don't you're going to have a number of insidious errors start occuring with system admin commands.
The correct location for data files would be either /var/tmp (perhaps a directory called /var/tmp/datafiles) or an application directory in /opt. The permission for the datafiles directory would be 775 with owner and group set appropriately. I would NOT use a user ID called operator except possibly for some backup administrator tasks. Every user has their own login for accountability and you add groups as needed for each user.
Bill Hassell, sysadmin
