Hi all, sorry for disturbing your time, i've got some question
2 user samba on network got problem on excel files, sometimes after
they update their files-save-and close that files, but when they open again that files the last input file had missing.

Is there any related on my cron scripts to chmod that files to 0775 every 5 minutes cause i've been try the smb.conf create mask or create mode but did'nt work on server OpenSuse 10.2 (i've been posted this related issue).

And can i know how to check what user samba open files? cause i've used lsof to check that and it work's but sometimes i've seen user root that open the files.

Need enlightment and advise please,

sorry for this question and thank's a lot.

Did you try "force create mode" in smb.conf? See http://us1.samba.org/samba/docs/man/...mb.conf.5.html and scan through for "force create".

Also, in watching what's going on in samba, have you tried smbstatus and/or upping the log level and watching the log files.

Use the the following command as root,

smbstatus

Look for the section labeled 'Locked files'.

Regards,

--
Prasanta

Hi Thanks for all your replies, hi choogendyk i've been tryed force create mode too
but didn't work at all, this kind of thing not happen when i used ubuntu server. the one thing
that i know is when configuration samba on open suse 10.2 must use Yast to configure it, cause
sometimes what i add on smb.conf using manually not shown on yast samba, correct me if i'm wrong.

Thank's a lot.

I'm not familiar enough with Yast or Suse to answer that question. Someone else will have to jump in.

However, since Yast is the install tool, and you aren't seeing your changes take place, I would look for one of two things. Either you are changing a different samba install than what is actually running, or Yast is stomping on your changes and reverting them.

An analogous confusion would be on Solaris 10 if you had the Sun installed Samba in /opt with the SMF service samba, but you had installed your own version of Samba in /usr/local and created an SMF service samba-local. In this case, you would have to make sure you do `svcadm disable samba` and `svcadm enable samba-local` and then make all changes to your /usr/local/samba/lib/smb.conf. If at some point you accidentally start Samba up again with `svcadm enable samba`, or some update causes it to re-enable, then you have confusion.

So, you'll have to explore a bit more what Yast is doing with Samba install and configuration, and answer whether you are doing something different that may conflict with it.