Hi there,
Had some problems with my jail's IP address having to change since I moved in with my wife - couldn't change it (was giving me a dialog concerning the NAME of the jail, which was grayed-out anyways, so I couldn't save) - anyways, decided to upgrade to 9.2.1.2 to start fresh.
But, that resuscitated a bunch of permissions issues that I remember having....and I'm now worse off than I was, as my CIFS won't even start. What I've done so far :
1. Tried what I remember (sorta) from the last time I built this machine, which was about a year and a half ago. That meant creating the share, and hoping everything worked;
2. Then, I followed the guide at
to the letter - the part about anonymous sharing. So now, I could create new files, but still couldn't overwrite current existing ones;
3. Out of desperation, I just SSH'd to the root folder of my share and went
Not sure if that's what it didn't like, but somewhere in my tinkering, my server got mad at me - and now, I can't even start CIFS! Testparm results :
Please help - this is enormously frustrating. One more note about the whole "too many files open" thing : if I tried opening files on the share (during the time it was available, of course) and I'd get a notification in Windows that the file was already open by another user, that I could only open a read-only copy.
Looking forward to your replies!
Had some problems with my jail's IP address having to change since I moved in with my wife - couldn't change it (was giving me a dialog concerning the NAME of the jail, which was grayed-out anyways, so I couldn't save) - anyways, decided to upgrade to 9.2.1.2 to start fresh.
But, that resuscitated a bunch of permissions issues that I remember having....and I'm now worse off than I was, as my CIFS won't even start. What I've done so far :
1. Tried what I remember (sorta) from the last time I built this machine, which was about a year and a half ago. That meant creating the share, and hoping everything worked;
2. Then, I followed the guide at
to the letter - the part about anonymous sharing. So now, I could create new files, but still couldn't overwrite current existing ones;
3. Out of desperation, I just SSH'd to the root folder of my share and went
chmod -R 777 *.*
Not sure if that's what it didn't like, but somewhere in my tinkering, my server got mad at me - and now, I can't even start CIFS! Testparm results :
Load smb config files from /usr/local/etc/smb4.conf
max_open_files: increasing sysctl_max (11095) to minimum Windows limit (16384)
rlimit_max: increasing rlimit_max (11095) to minimum Windows limit (16384)
Loaded services file OK.
WARNING: lock directory /var/db/samba4 should have permissions 0755 for browsing to work
WARNING: state directory /var/db/samba4 should have permissions 0755 for browsing to work
WARNING: cache directory /var/db/samba4 should have permissions 0755 for browsing to work
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions
[global]
dos charset = CP437
server string = FreeNAS Server
server role = standalone server
map to guest = Bad User
obey pam restrictions = Yes
smb passwd file = /var/etc/private/smbpasswd
private dir = /var/etc/private
max log size = 51200
time server = Yes
deadtime = 15
hostname lookups = Yes
load printers = No
printcap name = /dev/null
disable spoolss = Yes
dns proxy = No
pid directory = /var/run/samba
panic action = /usr/local/libexec/samba/samba-backtrace
idmap config * : backend = tdb
create mask = 0666
directory mask = 0777
directory name cache size = 0
map archive = No
map readonly = no
store dos attributes = Yes
strict locking = No
Please help - this is enormously frustrating. One more note about the whole "too many files open" thing : if I tried opening files on the share (during the time it was available, of course) and I'd get a notification in Windows that the file was already open by another user, that I could only open a read-only copy.
Looking forward to your replies!