search for: inotify_setup

Hi, I'm going through my messages log and I've noticed a large amount of the following error going on. What affect would this have on the smb client that is connected to those pid's? Mar 11 11:35:24 process1 smbd[25349]: [2010/03/11 11:35:24, 0] smbd/notify_inotify.c:293(inotify_setup) Mar 11 11:35:24 process1 smbd[25349]: Failed to init inotify - Too many open files Mar 11 11:35:24 process1 smbd[25349]: [2010/03/11 11:35:24, 0] smbd/notify_inotify.c:293(inotify_setup) Mar 11 11:35:24 process1 smbd[25349]: Failed to init inotify - Too many open files Mar 11 11:35:24 pro...

Hello, I've a problem on my system with inotify. In the smbd logfile are shown a lot messages like this: [2015/06/10 11:15:21.644453, 0, pid=57030, effective(12700, 100), real(0, 0)] smbd/notify_inotify.c:297(inotify_setup) Failed to init inotify - Too many open files [2015/06/10 11:15:23.968497, 0, pid=57030, effective(12700, 100), real(0, 0)] smbd/notify_inotify.c:297(inotify_setup) Failed to init inotify - Too many open files [2015/06/10 11:15:24.192444, 0, pid=57030, effective(12700, 100), real(0, 0)] smbd/noti...

Hi samba team, I my log I have sometimes this message : smbd/notify_inotify.c:inotify_setup(283) Failed to init inotify - Trop de fichiers ouverts : 2661 Time(s) Informations : Samba 3.2.4 (ldap backend and acl support) Redhat Enterprise Linux 5.1 (data on XFS FS) What's means ? Thanks Stephane Purnelle ----------------------------------- St?phane PURNELLE...

./configure --bundled-libraries && make ............ [3638/3880] Linking default/source4/lib/policy/py-policy.so [3639/3880] Linking default/source4/auth/ntlm/libauth4.so [3640/3880] Linking default/source4/ntvfs/libntvfs.so default/source4/ntvfs/sysdep/inotify_1.o: In function `inotify_setup': inotify.c:(.text+0x503): undefined reference to `inotify_init' default/source4/ntvfs/sysdep/inotify_1.o: In function `watch_destructor': inotify.c:(.text+0x883): undefined reference to `inotify_rm_watch' default/source4/ntvfs/sysdep/inotify_1.o: In function `inotify_watch': in...

.... [3591/3880] Linking default/source4/librpc/python-unixinfo.so [3592/3880] Linking default/source4/ntvfs/libntvfs.so default/source4/ntvfs/sysdep/inotify_1.o: In function `inotify_setup': inotify.c:(.text+0x508): undefined reference to `inotify_init' default/source4/ntvfs/sysdep/inotify_1.o: In function `watch_destructor': inotify.c:(.text+0x8d4): undefined reference to `inotify_rm_watch' default/source4/ntvfs/sysdep/inotify_1.o: In function `inotify_watch': in...

...urce4/lib/policy/py-policy.so [3410/3611] Linking default/source4/dsdb/samdb/ldb_modules/libldb-objectclass.so [3411/3611] Linking default/source4/dsdb/samdb/ldb_modules/libldb-descriptor.so [3412/3611] Linking default/source4/ntvfs/libntvfs.so default/source4/ntvfs/sysdep/inotify_1.o: In function `inotify_setup': inotify.c:(.text+0x508): undefined reference to `inotify_init' default/source4/ntvfs/sysdep/inotify_1.o: In function `watch_destructor': inotify.c:(.text+0x8d4): undefined reference to `inotify_rm_watch' default/source4/ntvfs/sysdep/inotify_1.o: In function `inotify_watch': in...

...0 after 3 usecs [ 38.127518] calling proc_filesystems_init+0x0/0x1a @ 1 [ 38.132808] initcall proc_filesystems_init+0x0/0x1a returned 0 after 1 usecs [ 38.139911] calling dnotify_init+0x0/0x6b @ 1 [ 38.144423] initcall dnotify_init+0x0/0x6b returned 0 after 5 usecs [ 38.150744] calling inotify_setup+0x0/0xd @ 1 [ 38.155250] initcall inotify_setup+0x0/0xd returned 0 after 0 usecs [ 38.161576] calling inotify_user_setup+0x0/0x9d @ 1 [ 38.166617] initcall inotify_user_setup+0x0/0x9d returned 0 after 13 usecs [ 38.173536] calling aio_setup+0x0/0x5f @ 1 [ 38.178541] initcall aio_setup+0...