Forum Home
Press F1
 
Thread ID: 53456 2005-01-18 05:39:00 Unix/Windows deleting issues Mike (15) Press F1
Post ID Timestamp Content User
315357 2005-01-18 08:06:00 Its going to tell me who owns what files so we can check permissions etc
We've checked and changed permissions left, right, & centre. Made me a superuser, almost everything you can think of to do with permissions, but the same thing happens. Usually if I try to delete/edit a file that isn't mine (even from Windows) I get a permissions error. However trying to delete files that I do have permissions for doesn't give an error, the file appears to delete, but just reappears on a refresh.

I'd say that samba is not using the correct groups etc when creating files or something similar
These could be files created either from Windows or from Unix, so that should be irrelevant to SAMBA shouldn't it? Some of the files I tried on were several months old, so were created and last edited long before this problem started.

Mike.
Mike (15)
315358 2005-01-18 09:52:00 I am just learning about Samba and I have a XP machine, FC 2 and Xandros machines seeing each other and the linux machines are using the printing share on the xp machine the reason Im telling you this is Samba does control alot of permissions regaurdless of normal file and directory ownerships in this kind of setup, I would be talking to that linux guru and see what hes been up to in smb.conf (control file for samba).
Another question I would ask is, did your trouble start when the linux guru started tinkering with samba ?
beama (111)
315359 2005-01-18 10:03:00 Another question I would ask is, did your trouble start when the linux guru started tinkering with samba ?

No, no, you misunderstand... he hasn't been "tinkering" with SAMBA - he's been working in there to try to solve our issues. Our organisation is big enough that the IS techies don't just "tinker" with settings.

We do (I think) have 2 or 3 other Unix servers, so I might suggest to him that he tests for the problem on those... it'll be interesting to see. He seems to think it's a Windows problem, possibly to do with recent updates or such, however only our Workstations are automatically updated - our servers have to be manually updated (for obvious reasons) and the issue occurs on both Win 2000 Workstation and server (and Win2003).

Mike.
Mike (15)
315360 2005-01-18 10:10:00 Sorry Mike wrong choice of word there "tinkering" was just a figure of speech
I actually wondered when reading this thread about windows updates.
beama (111)
315361 2005-01-18 10:26:00 Sorry Mike wrong choice of word there "tinkering" was just a figure of speech

Ah okay :) No, the "tinkering" ;) didn't start until I tried to get the problem fixed.

Cheers,
Mike.
Mike (15)
315362 2005-01-18 20:24:00 Its going to tell me who owns what files so we can check permissions etc

I'd say that samba is not using the correct groups etc when creating files or something similar

All the files in the folder I was looking at are owned by me, and the group is my group. This doesn't just happen in one directory, this happens in any directory on any drive for any user on the Unix server via Windows.

Mike.
Mike (15)
315363 2005-01-18 22:57:00 Can you post back
ls -la /home/user/dirname

-rw-rw-rw- 1 mike gis 46 Oct 11 15:19 ver.txt
-rwxrwxrwx 1 mike gis 132 Jan 17 11:04 z1.txt*
-rw-rw-r-- 1 mike gis 2852324 Jan 12 08:10 coach.eps

Those three files are three that we have tried deleting.

Mike.
Mike (15)
315364 2005-01-19 00:36:00 Sounds suspiciouly like a safety mechanism that has been activate/changed - like noclobber for cp in linux etc. Almost certainly in Solaris itself - not Samba or Windows. I do not know how Solaris implements this. Was anything changed in mid-Dec at the time this started happening? You say this also happens when you try to move/rename a file? Have you tried to overwrite a file? Try and tell us what happens. vinref (6194)
315365 2005-01-19 02:44:00 Ignore my post above. I just realised it is completely wrong. vinref (6194)
315366 2005-01-19 02:45:00 Sounds suspiciouly like a safety mechanism that has been activate/changed - like noclobber for cp in linux etc. Almost certainly in Solaris itself - not Samba or Windows. I do not know how Solaris implements this. Was anything changed in mid-Dec at the time this started happening? You say this also happens when you try to move/rename a file? Have you tried to overwrite a file? Try and tell us what happens.

I can rename files fine. I can move them, but instead of moving they just copy (eg the copy doesn't delete once it's moved). Overwriting the file works fine, as does opening and editing the contents of the file. I just can't remove the file.

Mike.
Mike (15)
1 2 3