It seems that vfs_readonly.so does not work. (1) apply to the patch attached (to display what happened). (2) set parameters in smb.conf: ----- [share1] ... vfs objects = readonly readonly:period = "today 21:40","today 23:40" (current time is 22:03) ----- (3) connect to share and view the log: ----- [2008/11/15 22:03:00, 0] modules/vfs_readonly.c:readonly_connect(71) period0 is 1226752800, period1 is 1226760000, current_time is 1226754180 [2008/11/15 22:03:00, 0] modules/vfs_readonly.c:readonly_connect(75) read only = True ----- vfs_readonly module determined "read only = True", but actually, I can write.
Created attachment 3736 [details] patch for displaying debug logs
Created attachment 3744 [details] Patch for 3.2.x This fixes the problem for me. Thanks ! Jeremy.
Patch #2 works for me, too. Thanks! This bug should be closed...
I tested againt Samba 3.2.6 and this bug is fixed at 3.2.6. (And not at 3.2.5) according to the announcement: http://samba.org/samba/history/samba-3.2.6.html ----- * BUG 5900: Fix vfs_readonly. ----- Thanks!