Samba bad file descriptor

You don't distinguish the two error cases in your code, both can fail select or accept. My guess is that you just have a time out and that select returns 0. In Linux once you create a connection and it get closed then you have to wait for some time before making new connection. As in Linux, socket doesn't release the port no. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams?

Collectives on Stack Overflow. Learn more. Linux server socket - Bad file descriptor Ask Question. Asked 9 years, 5 months ago. Active 6 years, 3 months ago. Viewed 32k times. There is nothing wrong with the code you posted, the error must be elsewhere. Do you use the socket after closing it for example?

Where are the threads exactly used? The above code runs in one thread. The other code is in another module which also runs a thread. Closing the connection there kills the server here. I hadn't thought that a server socket could become invalid without me closing it. My bet is that some bug in your code is causing you to close the very same socket you later select on.

I had successful connections from my main workstation PC which uses Fedora 29 Workstation to my mother's laptop Windows 7 HP network share few times using mount. Using mount -t cifs was also successful in the past but not anymore, since it returns an error as following:. Edit: someone from the community has noticed that official update fixing the problem has been released; this link provides a solution:.

Microsoft released the Update KB to fix the issue:. This does not affect domain accounts in the local "Administrators" group. So download and install the update by doing a double click on the msu file. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Asked 3 years ago. Active 2 years, 11 months ago. Viewed 5k times. Default has changed to a more secure dialect, SMB2.

The default is NO. A private printer, usable only by fred. Spool data will be placed in fred's home directory. Note that fred must have write access to the spool directory, wherever it is. Note that fred requires write access to the directory.

Note that all files created in the directory by users will be owned by the default user, so any user with access can delete any other user's files. Obviously this directory must be writable by the default user.

Another user could of course be specified, in which case all files would be owned by that user instead. In this setup, the directory should be writable by both users and should have the sticky bit set on it to prevent abuse. Obviously this could be extended to as many users as required. Pages: 1. Atom topic feed Powered by FluxBB.