Displaying 4 results from an estimated 4 matches for "scadenze".
2020 Mar 30
2
Could not delete share entry
...y for .
> [2020/03/30 15:00:51.389289, 0] ../../source3/smbd/close.c:1126(close_directory)
> close_directory: Could not get share mode lock for .
> [2020/03/30 15:04:26.306712, 0] ../../source3/smbd/close.c:1126(close_directory)
> close_directory: Could not get share mode lock for SCADENZE FORNITORI
> [2020/03/30 15:23:16.754076, 0] ../../source3/smbd/close.c:1214(close_directory)
> close_directory: Could not delete share entry for SCADENZE FORNITORI
bye & Thanks
av.
2020 Mar 30
2
Could not delete share entry
Hello.
I'm seeing several of the above messages in my smbd logs.
I see three different kinds:
> close_directory: Could not delete share entry for .
> close_directory: Could not delete share entry for {filename}
> close_remove_share_mode: Could not delete share entry for file {filename}
I could find no explanation on their meaning.
Anyone has a pointer?
bye & Thanks
av.
2020 Mar 31
2
Could not delete share entry
...e or directory
You mean, it's a client trying to delete a file/directory?
From what I can see, crossing smbd's log and audit log, the message
> [2020/03/30 15:23:16.754076, 0]
../../source3/smbd/close.c:1214(close_directory)
> close_directory: Could not delete share entry for SCADENZE FORNITORI
does not mean that client was trying to delete that folder.
Or is it rather an internal structure in Samba referencing a file/directory?
> and whilst it is
> probably a bit of a problem, I do not think it is a Samba problem.
Could you provide some pointer to what kind of...
2020 Mar 31
2
Could not delete share entry
On 2020-03-31 11:38, Rowland penny via samba wrote:
> I wouldn't worry about those, they are just warnings that something is
> trying to delete something that it shouldn't or cannot. i.e something
> that has already been deleted or it doesn't have the permission to delete.
Well, I guess so :)
Any hint on what that "something" is?
What is a "share