Broken Links for non-owner

[valdez]

Hi,

I am a noob, so I may be missing something obvious....

This seems to be a random problem.

From client (MAC / WIN7) I can see directories, but not files on some of my shares.

As root or owner (at server), I can see all folders and files.

As a non-owner (at server), files show-up as broken links.

I am using Grey Hole and suspect there is a relationship here, maybe how I copied files or implemented GH.

Any suggestions / ideas?

Valdez

[cpg]

without details we cannot help.

can you show listing of files (text) or screenshots, with LOTS of details, etc. etc.?

also *how* did you copied files to implement greyhole??
we cannot simply guess what you did and how you think this is related.

[valdez]

ok, good point.

Here are a couple of scr shots.

Kevo is not owner, but part of group.

valdez is owner.

The obvious differences are the "Octal Permissions" and "Type".
- Not sure what is causing the differences when looking at files as different users.

Files were copied over by using file manager (i.e. drag and drop), from my backup.

valdez

[gboudreau]

1. You should not have copied using the file manager. There's a big red warning against that in the Greyhole wiki page: http://wiki.amahi.org/index.php?title=Greyhole
This is probably why other users can't access the files you copied into your shares using the HDA, as Greyhole keeps the permissions of the original file, and your original files (from your backup) were probably only readable by the valdez user.

2. The permissions that are used to allow or not access to a file is the target of the link, not the permissions of the link itself.
So check where those links point to (in a Terminal, do "ls -l filename", or I guess checking the properties of the link in the file manager should show you), and check the permissions of that file. My guess: they are 700 or 600.

If that's the case, try changing the permissions for one of those file to '664' (which is the default for new files that are copied using the shares). Then see if the non-owner user can now read the file.

If that worked, you'll probably want to recursively change the permissions of all the files in your shares. If you post the full path to one of the file you changed the permission of to fix the problem, we'll be able to give you a Terminal command to fix all files easily.
It would be something like:

Code: Select all

find /var/hda/files/drives/*/gh/ -type f -exec chmod 664 '{}' \;

[valdez]

Hi, thanks for quick input.
I am still confused on a few things:
- If not to use terminal or file mgr, what is the best method? ( I am afraid I am missing something obvious, here.)
- I had already changed file permissions to "777" as displace in pics (still tried your suggestion, with same results)

A couple of other notes:
- Back-up drive was NTFS
- When all files were copied over in same manner, why would some have broken links and some not???


Also, after researching a little more, I tried the below two commands to check the status of GH: Are they the correct responses, I should be getting?

[root@servevaldez valdez]# chkconfig --list greyhole
greyhole 0:off 1:off 2:off 3:off 4:off 5:off 6:off
[root@servevaldez valdez]# service greyhole status
Greyhole is running.

[gboudreau]

Greyhole shares must be accessed using shares.
i.e. on a remote computer, you mount the share, and access it through there.

Your screenshots show the links, not the actual files.
It's the permissions of the actual files than needs to be changed. Links are always 777.
See my last message about how to find the actual files, and try to change the permissions of those.

[valdez]

Ok...
Now understand about using shares vs file mgr/command line (need to think in server vs stand-a-lone PC mode)
Links....I know better, I was looking right at the link and it didn't click.
With your help, all is working.
Sorry for being so thick...
Thank you for your time and patience.
valdez