I think you are too restrictive with your permissions. I don't see why you have set the permissions to 770 on the outputs folder. With my setup I have a images folder at ./<virtual_host/images/...
Type: Posts; User: redmk2; Keyword(s):
I think you are too restrictive with your permissions. I don't see why you have set the permissions to 770 on the outputs folder. With my setup I have a images folder at ./<virtual_host/images/...
Why would you think that your response to @TheFu's reply to your question " Am I correct?" was warranted? Your approach to the sharing scenario is at best, amateurish. Your experience as a "...
Respectfully, I disagree on both parts. The OP was looking for guidance on how to setup a Samba file server from a professional point of view. Not just a "slap dash get it up and running any way...
You are free to create a directory that is shared anyplace in the file system. These shared directories are not called "partitions" or "mountpoints". A partition is a section (part of) of a block...
The netbios name is the name that is always used to define a SMB resource (the share) as in //NETBIOS_NAME/SHARE_NAME. The hostname does not have to be the same as the netbios name. If you do not...
I told you where to put the data in post #4 and again in my last post. Put the users Office data at /srv/samba and their private data at /home. Go back and re-read my #4 post. There is a link...
I understand that you have 70 Windows clients that want to share their Office and PDF files. The Z: drive is just the mapping to wherever the shared directory is located on the server.
What I...
The Linux chroot is best used to isolate applications from the rest of the OS. It really won't secure the application itself, the users from themselves or from users outside the chroot environment. ...
The traditional approach to this is to have all of the shared directories at /srv/samba/. This way all of the shared directories are in one area. The home directories can also be in this area. ...
Yes! It should be no longer than 15 characters.
It is the eve of a national holiday here in the USA so I will not be able to properly respond for at least a day. I will provide examples and specific terminal commands then.
What we will be...
You can use file system (ext4 or ...) ownership and permissions to restrict the users use. You can set up a common group and assign inherited group permissions on a section of the file system tree. ...
Ahhhhhhhhhhhhhhhhhhh! "Well, to be honest..." should have come first. After all that mucking about, this turns out to be a school assignment. Assisting in homework is frowned upon on this forum. ...
This sure sounds like you need to use the async parameter in the /etc/exports files. The default is to use: sync which constantly sync's the files to the disk and flushes the buffers. This really...
If it works for you it works for me! :-)
You do that at the Samba server configuration. The file is /etc/samba/smb.conf. Post the content here and I will show you how to set up the share. Are you logged into the Windows machine as mike?
Desktops are not users. The users logged in to second desktop (or for that matter the first desktop) are what you add to the group. In other words you do not add machines (hosts).
Edit: My...
The problem requires several configuration changes. First you need to use a common group for all users of the directory. Then the you grant ownership by that common group to the shared directory....
And bab1, for goodness sake
Really? Isn't this "Windows advice"?[/QUOTE]
I think it's just good advice whether it's Windows or Linux. A disk with a partition with a blank filesystem is the...
The software you mention is not needed to configure the WS MyCloud NAS. The device has all of the various file server protocols. See...
+1 to all that @bab1 has said.
One thing to add. If the share is set up properly then root_squash is in effect and you can't su to the root user and modify the files. Google: root squash NFS to...
At all times, for almost everything, the root user can take any action on a host. No theory, any file system that is mounted locally can be manipulated by the root user. Sudo or su is the mechanism...
It is not possible for just anybody to change theirs or anybody else's uid. On most production NFS servers the only user logins are for systems administrators. It is true that if you are the root...
I know what the OP had to do to cure it. Now you know too.
Use 13.04