Hola gente!!! Tengo montado samba sobre Sarge, con un directorio compartido con los ficheros de firmas del antivus, para que las m�quinas windows se actualicen.
Sin embargo tengo muchos errores: Jan 17 17:30:43 ProxyCC smbd[19911]: Error was Operaci�n no permitida Jan 17 17:30:43 ProxyCC smbd[19911]: [2005/01/17 17:30:43, 0] smbd/open.c:open_mode_check(675) Jan 17 17:30:43 ProxyCC smbd[19911]: open_mode_check: FAILED when breaking oplock (3) on file PAV.SIG, dev = 301, inode = 1762575 Jan 17 17:30:52 ProxyCC smbd[19911]: [2005/01/17 17:30:52, 0] smbd/oplock.c:request_oplock_break(1016) Jan 17 17:30:52 ProxyCC smbd[19911]: request_oplock_break: failed when sending a oplock break message to pid 19913 on port 34223 for dev = 301, inode = 1762575, file_id = 19 Jan 17 17:30:52 ProxyCC smbd[19911]: Error was Operaci�n no permitida Jan 17 17:30:52 ProxyCC smbd[19911]: [2005/01/17 17:30:52, 0] smbd/open.c:open_mode_check(675) Jan 17 17:30:52 ProxyCC smbd[19911]: open_mode_check: FAILED when breaking oplock (3) on file PAV.SIG, dev = 301, inode = 1762575 ProxyCC:/etc# tail /var/log/syslog Jan 17 17:30:43 ProxyCC smbd[19911]: [2005/01/17 17:30:43, 0] smbd/oplock.c:request_oplock_break(1016) Jan 17 17:30:43 ProxyCC smbd[19911]: request_oplock_break: failed when sending a oplock break message to pid 19913 on port 34223 for dev = 301, inode = 1762575, file_id = 19 Jan 17 17:30:43 ProxyCC smbd[19911]: Error was Operaci�n no permitida Jan 17 17:30:43 ProxyCC smbd[19911]: [2005/01/17 17:30:43, 0] smbd/open.c:open_mode_check(675) Jan 17 17:30:43 ProxyCC smbd[19911]: open_mode_check: FAILED when breaking oplock (3) on file PAV.SIG, dev = 301, inode = 1762575 Jan 17 17:30:52 ProxyCC smbd[19911]: [2005/01/17 17:30:52, 0] smbd/oplock.c:request_oplock_break(1016) Jan 17 17:30:52 ProxyCC smbd[19911]: request_oplock_break: failed when sending a oplock break message to pid 19913 on port 34223 for dev = 301, inode = 1762575, file_id = 19 Jan 17 17:30:52 ProxyCC smbd[19911]: Error was Operaci�n no permitida Jan 17 17:30:52 ProxyCC smbd[19911]: [2005/01/17 17:30:52, 0] smbd/open.c:open_mode_check(675) Jan 17 17:30:52 ProxyCC smbd[19911]: open_mode_check: FAILED when breaking oplock (3) on file PAV.SIG, dev = 301, inode = 1762575 ProxyCC:/etc# tail /var/log/syslog Jan 17 17:56:13 ProxyCC smbd[19924]: [2005/01/17 17:56:13, 0] smbd/oplock.c:request_oplock_break(1016) Jan 17 17:56:13 ProxyCC smbd[19924]: request_oplock_break: failed when sending a oplock break message to pid 20160 on port 34240 for dev = 301, inode = 1762575, file_id = 12 Jan 17 17:56:13 ProxyCC smbd[19924]: Error was Operaci�n no permitida Jan 17 17:56:13 ProxyCC smbd[19924]: [2005/01/17 17:56:13, 0] smbd/open.c:open_mode_check(675) Jan 17 17:56:13 ProxyCC smbd[19924]: open_mode_check: FAILED when breaking oplock (3) on file PAV.SIG, dev = 301, inode = 1762575 Jan 17 17:56:36 ProxyCC smbd[20167]: [2005/01/17 17:56:36, 0] smbd/oplock.c:request_oplock_break(1016) Jan 17 17:56:36 ProxyCC smbd[20167]: request_oplock_break: failed when sending a oplock break message to pid 20160 on port 34240 for dev = 301, inode = 1762575, file_id = 12 Estos errores hacen que muchas veces los clientes fallen en la actualizaci�n y salen mensajitos de error muy molestos. La verdad es que he buscando en google y no he encontrado ninguna pista sobre este error. Muchas gracias a todos por lo que podais aportar.
