From nf2@scheinwelt.at Wed May 5 12:04:45 2004 Received: with ECARTIS (v1.0.0; list fam); Wed, 05 May 2004 12:04:46 -0700 (PDT) Received: from mx-00.sil.at (mx-00.sil.at [62.116.68.196]) by oss.sgi.com (8.12.10/8.12.9) with SMTP id i45J4hKO002989 for ; Wed, 5 May 2004 12:04:44 -0700 Received: (qmail-ldap/ctrl 24846 invoked from network); 5 May 2004 19:04:39 -0000 Received: from unknown (HELO [192.168.5.9]) ([62.116.122.20]) (envelope-sender ) by mx-00.sil.at (qmail-ldap-1.03) with SMTP for ; 5 May 2004 19:04:39 -0000 Subject: Signal to suspend all monitors for a while From: nf Reply-To: nf2@scheinwelt.at To: fam@oss.sgi.com Content-Type: text/plain Message-Id: <1083783882.3751.59.camel@lilota.lamp.priv> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6-2mdk Date: Wed, 05 May 2004 21:04:42 +0200 Content-Transfer-Encoding: 7bit X-archive-position: 232 X-ecartis-version: Ecartis v1.0.0 Sender: fam-bounce@oss.sgi.com Errors-to: fam-bounce@oss.sgi.com X-original-sender: nf2@scheinwelt.at Precedence: bulk X-list: fam Hi! I'm currently working on a little tool to assist people with their "umount - device is busy" problems. http://www.scheinwelt.at/~norbertf/wbumount/ AFAIK "fam" plays a major role when people get in this kind of trouble. Would it be technically possible to send "fam" a signal to suspend ALL monitors for a certain time-period (2-5 secs?). So that there is enough time to do the umount? I would then add a little suid-root command to wbumount to send the signal. I know this sounds like a dirty fix, but it would probably be easier than writing a full featured control- and status api (Which would still be quite useful...). Norbert From Francois.Bolduc@consulting.fujitsu.com Tue May 11 12:20:00 2004 Received: with ECARTIS (v1.0.0; list fam); Tue, 11 May 2004 12:20:14 -0700 (PDT) Received: from canada-smtp1.consulting.fujitsu.com (canada-smtp1.consulting.fujitsu.com [198.168.250.2]) by oss.sgi.com (8.12.10/8.12.9) with SMTP id i4BJJxKO025941 for ; Tue, 11 May 2004 12:20:00 -0700 Received: from Montreal-NS002.DMR.CA ([205.151.154.84]) by canada-smtp1.consulting.fujitsu.com (Lotus Domino Release 6.0.3) with ESMTP id 2004051115202948-155689 ; Tue, 11 May 2004 15:20:29 -0400 Subject: fam 2.7.0 compile error on Solaris 9 (i386) To: fam@oss.sgi.com X-Mailer: Lotus Notes Release 5.0.11 July 24, 2002 Message-ID: From: Francois.Bolduc@consulting.fujitsu.com Date: Tue, 11 May 2004 15:16:03 -0400 MIME-Version: 1.0 X-MIMETrack: Serialize by Router on Montreal-NS002/DMR/CA(Release 5.0.11 |July 24, 2002) at 05/11/2004 03:18:47 PM, Itemize by SMTP Server on Canada-SMTP1/EXT/US(Release 6.0.3|September 26, 2003) at 05/11/2004 03:20:29 PM, Serialize by Router on Canada-SMTP1/EXT/US(Release 6.0.3|September 26, 2003) at 05/11/2004 03:20:45 PM, Serialize complete at 05/11/2004 03:20:45 PM Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id i4BJJxKO025941 X-archive-position: 233 X-ecartis-version: Ecartis v1.0.0 Sender: fam-bounce@oss.sgi.com Errors-to: fam-bounce@oss.sgi.com X-original-sender: Francois.Bolduc@consulting.fujitsu.com Precedence: bulk X-list: fam Hi there, I am attempting to build Gnome 2.6 for Solaris 9 on Intel and fam (libfam) is part of the pre-requisites. Browsing around newsgroups and Google search archives, I have found that some fixing is required to get a successful configure and make. I am trying to compile with gcc 3.3.2. 1) "sun" keyword I changed all variable references to the "sun" keyword to dsun. The following files were affected: ./lib/Client.c++ ./src/TCP_Client.h ./src/ClientConnection.c++ ./src/ClientConnection.h ./src/LocalClient.h ./src/Listener.c++ ./src/LocalClient.c++ 2) u_int32_t and uint32_t Sun libraries include uint32_t and not u_int32_t. I have replaced the references of u_int32_t with uint32_t. The following files were affected: ./lib/Client.c++ ./src/NetConnection.h 3) Running make now generates the following results: # make cd . && /bin/bash /tmp/fam-2.7.0/missing --run aclocal-1.6 /tmp/fam-2.7.0/missing: aclocal-1.6: command not found WARNING: `aclocal-1.6' is missing on your system. You should only need it if you modified `acinclude.m4' or `configure.ac'. You might want to install the `Automake' and `Perl' packages. Grab them from any GNU archive site. cd . && \ /bin/bash /tmp/fam-2.7.0/missing --run automake-1.6 --gnu Makefile /tmp/fam-2.7.0/missing: automake-1.6: command not found WARNING: `automake-1.6' is missing on your system. You should only need it if you modified `Makefile.am', `acinclude.m4' or `configure.ac'. You might want to install the `Automake' and `Perl' packages. Grab them from any GNU archive site. cd . && /bin/bash /tmp/fam-2.7.0/missing --run autoconf /bin/bash ./config.status --recheck running /bin/bash ./configure --prefix=/opt/sfw CC=gcc CFLAGS=-O -g CPPFLAGS=-I /opt/sfw/include -I/usr/local/include -I/opt/csw/include -I/opt/sfw/share/includ e -I/usr/sfw/include -I/usr/local/ssl/include -I/usr/include -I/usr/openwin/shar e/include -I/usr/xpg4/include -I/usr/dt/share/include -I/usr/j2se/include -I/opt /sfw/mysql/include -I/usr/java/include -I/usr/kde/include -I/usr/ucbinclude LDFL AGS =-L/opt/sfw/lib:/usr/local/lib:/opt/csw/lib:/usr/sfw/lib:/usr/local/ssl/lib:/ usr/java/jre/lib/i386:/usr/kde/lib:/opt/csw/lib:/lib:/usr/lib:/usr/local/share --no-create --no-recursion checking for a BSD-compatible install... /usr/local/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for g++... g++ checking for C++ compiler default output... a.out checking whether the C++ compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking for style of include used by make... GNU checking dependency style of g++... gcc3 checking for gcc... gcc checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking dependency style of gcc... gcc3 checking how to run the C preprocessor... gcc -E checking build system type... i386-pc-solaris2.9 checking host system type... i386-pc-solaris2.9 checking for ld used by GCC... /usr/ccs/bin/ld checking if the linker (/usr/ccs/bin/ld) is GNU ld... no checking for /usr/ccs/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/ccs/bin/nm -p checking for a sed that does not truncate output... /opt/sfw/bin/sed checking whether ln -s works... yes checking how to recognise dependent libraries... pass_all checking command to parse /usr/ccs/bin/nm -p output... ok checking how to run the C++ preprocessor... g++ -E checking for egrep... egrep checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... no checking for unistd.h... yes checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking for ranlib... ranlib checking for strip... strip checking for objdir... .libs checking for gcc option to produce PIC... -fPIC checking if gcc PIC flag -fPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... no checking if we can lock with hard links... yes checking if gcc supports -fno-rtti -fno-exceptions... yes checking whether the linker (/usr/ccs/bin/ld) supports shared libraries... yes checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... no checking dynamic linker characteristics... solaris2.9 ld.so checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes creating libtool checking for a BSD-compatible install... /usr/local/bin/install -c checking whether ln -s works... yes checking whether make sets $(MAKE)... (cached) yes checking for pmap_set in -lrpcsvc... no checking for ANSI C header files... (cached) yes checking for dirent.h that defines DIR... yes checking for library containing opendir... none required checking fcntl.h usability... yes checking fcntl.h presence... yes checking for fcntl.h... yes checking limits.h usability... yes checking limits.h presence... yes checking for limits.h... yes checking linux/imon.h usability... no checking linux/imon.h presence... no checking for linux/imon.h... no checking netinet/in.h usability... yes checking netinet/in.h presence... yes checking for netinet/in.h... yes checking rpc/rpc.h usability... yes checking rpc/rpc.h presence... yes checking for rpc/rpc.h... yes checking rpcsvc/mount.h usability... yes checking rpcsvc/mount.h presence... yes checking for rpcsvc/mount.h... yes checking stddef.h usability... yes checking stddef.h presence... yes checking for stddef.h... yes checking for stdlib.h... (cached) yes checking for string.h... (cached) yes checking syslog.h usability... yes checking syslog.h presence... yes checking for syslog.h... yes checking sys/imon.h usability... no checking sys/imon.h presence... no checking for sys/imon.h... no checking sys/param.h usability... no checking sys/param.h presence... yes configure: WARNING: sys/param.h: present but cannot be compiled configure: WARNING: sys/param.h: check for missing prerequisite headers? configure: WARNING: sys/param.h: proceeding with the preprocessor's result configure: WARNING: ## ------------------------------------ ## configure: WARNING: ## Report this to bug-autoconf@gnu.org. ## configure: WARNING: ## ------------------------------------ ## checking for sys/param.h... yes checking sys/select.h usability... yes checking sys/select.h presence... yes checking for sys/select.h... yes checking sys/statvfs.h usability... yes checking sys/statvfs.h presence... yes checking for sys/statvfs.h... yes checking sys/syssgi.h usability... no checking sys/syssgi.h presence... no checking for sys/syssgi.h... no checking sys/time.h usability... yes checking sys/time.h presence... yes checking for sys/time.h... yes checking for sys/types.h... (cached) yes checking sys/un.h usability... yes checking sys/un.h presence... yes checking for sys/un.h... yes checking for unistd.h... (cached) yes checking for stdbool.h that conforms to C99... no checking for _Bool... no checking for bool... yes checking for socklen_t... no checking for an ANSI C-conforming const... yes checking for uid_t in sys/types.h... yes checking for inline... inline checking for pid_t... yes checking for size_t... yes checking whether time.h and sys/time.h may both be included... yes checking for struct sockaddr.sa_len... no checking for error_at_line... no checking for sys/select.h... (cached) yes checking sys/socket.h usability... yes checking sys/socket.h presence... yes checking for sys/socket.h... yes checking types of arguments for select... int,fd_set *,struct timeval * checking for bindresvport... no checking for _daemonize... no checking for daemon... no checking for getgrmember... no checking for select... no configure: creating ./config.status cd . && /bin/bash ./config.status Makefile config.status: creating Makefile cd . && /bin/sh /tmp/fam-2.7.0/missing --run autoheader touch ./config.h.in cd . && /bin/sh ./config.status config.h config.status: creating config.h config.status: config.h is unchanged make all-recursive make[1]: Entering directory `/tmp/fam-2.7.0' Making all in include make[2]: Entering directory `/tmp/fam-2.7.0/include' cd .. && /bin/bash ./config.status include/Makefile config.status: creating include/Makefile make[2]: Leaving directory `/tmp/fam-2.7.0/include' make[2]: Entering directory `/tmp/fam-2.7.0/include' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/tmp/fam-2.7.0/include' Making all in lib make[2]: Entering directory `/tmp/fam-2.7.0/lib' cd .. && /bin/bash ./config.status lib/Makefile depfiles config.status: creating lib/Makefile config.status: executing depfiles commands make[2]: Leaving directory `/tmp/fam-2.7.0/lib' make[2]: Entering directory `/tmp/fam-2.7.0/lib' source='Client.c++' object='Client.lo' libtool=yes \ depfile='.deps/Client.Plo' tmpdepfile='.deps/Client.TPlo' \ depmode=gcc3 /bin/sh ../depcomp \ /bin/sh ../libtool --mode=compile g++ -DHAVE_CONFIG_H -I. -I. -I.. -I../include -DFAM_CONF=\"/opt/sfw/etc/fam.conf\" -I/opt/sfw/include -I/usr/local/include -I /opt/csw/include -I/opt/sfw/share/include -I/usr/sfw/include -I/usr/local/ssl/in clude -I/usr/include -I/usr/openwin/share/include -I/usr/xpg4/include -I/usr/dt/ share/include -I/usr/j2se/include -I/opt/sfw/mysql/include -I/usr/java/include - I/usr/kde/include -I/usr/ucbinclude -g -O2 -c -o Client.lo `test -f 'Client.c++ ' || echo './'`Client.c++ mkdir .libs g++ -DHAVE_CONFIG_H -I. -I. -I.. -I../include -DFAM_CONF =\"/opt/sfw/etc/fam.conf \" -I/opt/sfw/include -I/usr/local/include -I/opt/csw/include -I/opt/sfw/share/i nclude -I/usr/sfw/include -I/usr/local/ssl/include -I/usr/include -I/usr/openwin /share/include -I/usr/xpg4/include -I/usr/dt/share/include -I/usr/j2se/include - I/opt/sfw/mysql/include -I/usr/java/include -I/usr/kde/include -I/usr/ucbinclude -g -O2 -c Client.c++ -MT Client.lo -MD -MP -MF .deps/Client.TPlo -fPIC -DPIC In file included from /usr/local/include/c++/3.3.2/backward/iostream.h:31, from Client.c++:37: /usr/local/include/c++/3.3.2/backward/backward_warning.h:32:2: warning: #warning This file includes at least one deprecated or antiquated header. Please conside r using one of the 32 headers found in section 17.4.1.2 of the C++ standard. Exa mples include substituting the header for the header for C++ includes, or instead of the deprecated header . To disable this wa rning use -Wno-deprecated. In file included from /usr/local/include/c++/3.3.2/i386-pc-solaris2.9/bits/c++io .h:35, from /usr/local/include/c++/3.3.2/bits/fpos.h:44, from /usr/local/include/c++/3.3.2/iosfwd:49, from /usr/local/include/c++/3.3.2/ios:44, from /usr/local/include/c++/3.3.2/ostream:45, from /usr/local/include/c++/3.3.2/iostream:45, from /usr/local/include/c++/3.3.2/backward/iostream.h:32, from Client.c++:37: /usr/local/include/c++/3.3.2/cstdio:137: error: `tmpfile' not declared /usr/local/include/c++/3.3.2/cstdio:138: error: `tmpnam' not declared In file included from /usr/local/include/c++/3.3.2/i386-pc-solaris2.9/bits/gthr- default.h:37, from /usr/local/include/c++/3.3.2/i386-pc-solaris2.9/bits/gthr. h:98, from /usr/local/include/c++/3.3.2/i386-pc-solaris2.9/bits/c++io .h:37, from /usr/local/include/c++/3.3.2/bits/fpos.h:44, from /usr/local/include/c++/3.3.2/iosfwd:49, from /usr/local/include/c++/3.3.2/ios:44, from /usr/local/include/c++/3.3.2/ostream:45, from /usr/local/include/c++/3.3.2/iostream:45, from /usr/local/include/c++/3.3.2/backward/iostream.h:32, from Client.c++:37: /usr/include/pthread.h:173: error: `pthread_t' was not declared in this scope /usr/include/pthread.h:173: error: parse error before `,' token /usr/include/pthread.h:174: error: `pthread_create' declared as function returning a function /usr/include/pthread.h:174: error: parse error before `void' /usr/include/pthread.h:175: error: `pthread_once_t' was not declared in this scope /usr/include/pthread.h:175: error: parse error before `,' token /usr/include/pthread.h:175: error: `pthread_once' declared as function returning a function /usr/include/pthread.h: In function `int pthread_once(...)': /usr/include/pthread.h:175: error: parse error before `)' token /usr/include/pthread.h:176: error: `pthread_t' undeclared (first use this function) /usr/include/pthread.h:176: error: (Each undeclared identifier is reported only once for each function it appears in.) /usr/include/pthread.h:176: error: parse error before `*' token /usr/include/pthread.h:180: error: parse error before `,' token /usr/include/pthread.h:181: error: parse error before `*' token /usr/include/pthread.h:185: error: initializer list being treated as compound expression /usr/include/pthread.h:186: error: `pthread_key_t' undeclared (first use this function) /usr/include/pthread.h:186: error: parse error before `,' token /usr/include/pthread.h:186: error: `pthread_key_create' declared as function returning a function /usr/include/pthread.h: In function `int pthread_key_create(...)': /usr/include/pthread.h:186: error: parse error before `)' token /usr/include/pthread.h:188: error: parse error before `void' /usr/include/pthread.h:190: error: syntax error before `(' token /usr/include/pthread.h:195: error: `pthread_mutexattr_t' undeclared (first use this function) /usr/include/pthread.h:195: error: parse error before `)' token /usr/include/pthread.h:196: error: parse error before `)' token /usr/include/pthread.h:197: error: parse error before `,' token /usr/include/pthread.h:198: error: parse error before `*' token /usr/include/pthread.h:199: error: parse error before `,' token /usr/include/pthread.h:200: error: parse error before `*' token /usr/include/pthread.h:201: error: parse error before `,' token /usr/include/pthread.h:202: error: parse error before `*' token /usr/include/pthread.h:203: error: parse error before `,' token /usr/include/pthread.h:204: error: parse error before `*' token /usr/include/pthread.h:205: error: `pthread_mutex_t' undeclared (first use this function) /usr/include/pthread.h:205: error: parse error before `,' token /usr/include/pthread.h:206: error: parse error before `)' token /usr/include/pthread.h:207: error: parse error before `)' token /usr/include/pthread.h:208: error: parse error before `)' token /usr/include/pthread.h:209: error: parse error before `)' token /usr/include/pthread.h:210: error: parse error before `)' token /usr/include/pthread.h:211: error: parse error before `,' token /usr/include/pthread.h:212: error: parse error before `*' token /usr/include/pthread.h:213: error: `pthread_condattr_t' undeclared (first use this function) /usr/include/pthread.h:213: error: parse error before `)' token /usr/include/pthread.h:214: error: parse error before `)' token /usr/include/pthread.h:215: error: parse error before `,' token /usr/include/pthread.h:216: error: parse error before `*' token /usr/include/pthread.h:217: error: `pthread_cond_t' undeclared (first use this function) /usr/include/pthread.h:217: error: parse error before `,' token /usr/include/pthread.h:218: error: parse error before `)' token /usr/include/pthread.h:219: error: parse error before `)' token /usr/include/pthread.h:220: error: parse error before `)' token /usr/include/pthread.h:221: error: parse error before `,' token /usr/include/pthread.h:222: error: parse error before `,' token /usr/include/pthread.h:224: error: parse error before `,' token /usr/include/pthread.h:230: error: parse error before `,' token /usr/include/pthread.h:231: error: parse error before `*' token /usr/include/pthread.h:232: error: `pthread_rwlock_t' undeclared (first use this function) /usr/include/pthread.h:232: error: parse error before `,' token /usr/include/pthread.h:234: error: parse error before `)' token /usr/include/pthread.h:235: error: parse error before `)' token /usr/include/pthread.h:236: error: parse error before `)' token /usr/include/pthread.h:237: error: parse error before `)' token /usr/include/pthread.h:238: error: parse error before `)' token /usr/include/pthread.h:239: error: parse error before `)' token /usr/include/pthread.h:240: error: `pthread_rwlockattr_t' undeclared (first use this function) /usr/include/pthread.h:240: error: parse error before `)' token /usr/include/pthread.h:241: error: parse error before `)' token /usr/include/pthread.h:242: error: parse error before `*' token /usr/include/pthread.h:243: error: parse error before `,' token In file included from /usr/local/include/c++/3.3.2/i386-pc-solaris2.9/bits/gthr. h:98, from /usr/local/include/c++/3.3.2/i386-pc-solaris2.9/bits/c++io .h:37, from /usr/local/include/c++/3.3.2/bits/fpos.h:44, from /usr/local/include/c++/3.3.2/iosfwd:49, from /usr/local/include/c++/3.3.2/ios:44, from /usr/local/include/c++/3.3.2/ostream:45, from /usr/local/include/c++/3.3.2/iostream:45, from /usr/local/include/c++/3.3.2/backward/iostream.h:32, from Client.c++:37: /usr/local/include/c++/3.3.2/i386-pc-solaris2.9/bits/gthr-default.h:40: error: s yntax error before `;' token /usr/local/include/c++/3.3.2/i386-pc-solaris2.9/bits/gthr-default.h:41: error: s yntax error before `;' token /usr/local/include/c++/3.3.2/i386-pc-solaris2.9/bits/gthr-default.h:42: error: s yntax error before `;' token /usr/local/include/c++/3.3.2/i386-pc-solaris2.9/bits/gthr-default.h:89: error: c annot declare static function inside another function /usr/local/include/c++/3.3.2/i386-pc-solaris2.9/bits/gthr-default.h: In function `int __gthread_active_p()': /usr/local/include/c++/3.3.2/i386-pc-solaris2.9/bits/gthr-default.h:450: error: ` __gthread_once_t' undeclared (first use this function) /usr/local/include/c++/3.3.2/i386-pc-solaris2.9/bits/gthr-default.h:450: error: ` once' undeclared (first use this function) /usr/local/include/c++/3.3.2/i386-pc-solaris2.9/bits/gthr-default.h:450: error: ` func' undeclared (first use this function) /usr/local/include/c++/3.3.2/i386-pc-solaris2.9/bits/gthr-default.h:450: error: parse error before `)' token /usr/local/include/c++/3.3.2/i386-pc-solaris2.9/bits/gthr-default.h:450: error: ` __gthread_once' declared as an `inline' variable /usr/local/include/c++/3.3.2/i386-pc-solaris2.9/bits/gthr-default.h:450: error: initializer list being treated as compound expression /usr/local/include/c++/3.3.2/i386-pc-solaris2.9/bits/gthr-default.h:450: confuse d by earlier errors, bailing out make[2]: *** [Client.lo] Error 1 make[2]: Leaving directory `/tmp/fam-2.7.0/lib' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/tmp/fam-2.7.0' make: *** [all] Error 2 # Any hints as what to try next? Thanks François Bolduc SCSA, SCNA Fujitsu Consulting 600-360 Albert St Ottawa Ontario K1R 7X7 Phone (613) 238-2697 x3736 Fax (613) 238-2802 http://www.fujitsu.com/ca From Jean-Marc.Valin@USherbrooke.ca Thu May 27 00:52:15 2004 Received: with ECARTIS (v1.0.0; list fam); Thu, 27 May 2004 00:52:19 -0700 (PDT) Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by oss.sgi.com (8.12.10/8.12.9) with SMTP id i4R7qCgi010064 for ; Thu, 27 May 2004 00:52:15 -0700 Received: from [192.168.1.12] ([69.70.229.201]) by VL-MO-MR005.ip.videotron.ca (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep 8 2003)) with ESMTP id <0HYD000QM4G52J@VL-MO-MR005.ip.videotron.ca> for fam@oss.sgi.com; Thu, 27 May 2004 03:50:29 -0400 (EDT) Date: Thu, 27 May 2004 03:50:29 -0400 From: Jean-Marc Valin Subject: fam using lots of CPU To: fam@oss.sgi.com Message-id: <1085644229.3221.16.camel@idefix.homelinux.org> Organization: =?ISO-8859-1?Q?Universit=E9?= de Sherbrooke MIME-version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Content-type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by oss.sgi.com id i4R7qCgi010064 X-archive-position: 234 X-ecartis-version: Ecartis v1.0.0 Sender: fam-bounce@oss.sgi.com Errors-to: fam-bounce@oss.sgi.com X-original-sender: Jean-Marc.Valin@USherbrooke.ca Precedence: bulk X-list: fam Hi, I'm having problems with fam on my machine (Fedora Core 2). When running one of my programs and redirecting stdout to a file, fam ends up eating all the CPU. During a normal run, my program takes 10 seconds of CPU while sneding 6.7 MB of data to stdout (which ends up in a file). In the meantime, fam ended up using 2 minutes(!!) of CPU: 12x more than the program it's monitoring. The file I'm writing is on a local filesystem and I have no filemanager open. Also, I've been able to see that if I remove the prints, fam no longer eats CPU. Anyone can help? I can provide more info if necessary. Please add me in CC to the reply since I'm not on the list. Jean-Marc -- Jean-Marc Valin http://www.xiph.org/~jm/ LABORIUS Université de Sherbrooke, Québec, Canada From nf2@scheinwelt.at Thu May 27 11:51:59 2004 Received: with ECARTIS (v1.0.0; list fam); Thu, 27 May 2004 11:52:04 -0700 (PDT) Received: from mx-00.sil.at (mx-00.sil.at [62.116.68.196]) by oss.sgi.com (8.12.10/8.12.9) with SMTP id i4RIprgi007986 for ; Thu, 27 May 2004 11:51:59 -0700 Received: (qmail-ldap/ctrl 18350 invoked from network); 27 May 2004 18:51:44 -0000 Received: from unknown (HELO [192.168.5.9]) ([62.116.122.20]) (envelope-sender ) by mx-00.sil.at (qmail-ldap-1.03) with SMTP for ; 27 May 2004 18:51:44 -0000 Subject: Re: fam using lots of CPU From: nf Reply-To: nf2@scheinwelt.at To: Jean-Marc Valin Cc: fam@oss.sgi.com, Nautilus mailing In-Reply-To: <1085644229.3221.16.camel@idefix.homelinux.org> References: <1085644229.3221.16.camel@idefix.homelinux.org> Content-Type: text/plain Message-Id: <1085683907.3438.54.camel@lilota.lamp.priv> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6-2mdk Date: Thu, 27 May 2004 20:51:47 +0200 Content-Transfer-Encoding: 7bit X-archive-position: 235 X-ecartis-version: Ecartis v1.0.0 Sender: fam-bounce@oss.sgi.com Errors-to: fam-bounce@oss.sgi.com X-original-sender: nf2@scheinwelt.at Precedence: bulk X-list: fam On Thu, 2004-05-27 at 09:50, Jean-Marc Valin wrote: > Hi, > > I'm having problems with fam on my machine (Fedora Core 2). When running > one of my programs and redirecting stdout to a file, fam ends up eating > all the CPU. During a normal run, my program takes 10 seconds of CPU > while sneding 6.7 MB of data to stdout (which ends up in a file). In the > meantime, fam ended up using 2 minutes(!!) of CPU: 12x more than the > program it's monitoring. The file I'm writing is on a local filesystem > and I have no filemanager open. Also, I've been able to see that if I > remove the prints, fam no longer eats CPU. > > Anyone can help? I can provide more info if necessary. Please add me in > CC to the reply since I'm not on the list. > > Jean-Marc Hi! It would be interesting if fam is monitoring the directory you are working in. Check $ fuser -v /directory or $ lsof | grep /directory under root. I was able to reproduce your experience by executing $ time bash -c "for ((a=1;a<100000;a++)); do echo \"test $a\"; done > test.txt" in a directory beeing watched/not being watched by fam (and nautilus). with fam: 0:30.44elapsed 12%CPU (the rest goes to fam 45% and nautilus 40%) without fam: 0:03.47elapsed 98%CPU Your experience is backing my impression that file alteration monitoring via events (kernel directory notification using dnotify) is less efficient than people tend to expect... What you could try: to disable fam in xinetd or recompile fam without the dnotify patch. Norbert From Jean-Marc.Valin@USherbrooke.ca Thu May 27 12:06:01 2004 Received: with ECARTIS (v1.0.0; list fam); Thu, 27 May 2004 12:06:05 -0700 (PDT) Received: from smtpi1.usherbrooke.ca (smtpi1.USherbrooke.ca [132.210.244.92]) by oss.sgi.com (8.12.10/8.12.9) with SMTP id i4RJ60gi009522 for ; Thu, 27 May 2004 12:06:00 -0700 Received: from [192.168.1.48] (laborius1.gel.usherb.ca [132.210.72.151]) by smtpi1.usherbrooke.ca (8.12.10/8.12.10) with ESMTP id i4RJ5euU017084; Thu, 27 May 2004 15:05:40 -0400 Subject: Re: fam using lots of CPU From: Jean-Marc Valin To: nf2@scheinwelt.at Cc: fam@oss.sgi.com, Nautilus mailing In-Reply-To: <1085683907.3438.54.camel@lilota.lamp.priv> References: <1085644229.3221.16.camel@idefix.homelinux.org> <1085683907.3438.54.camel@lilota.lamp.priv> Content-Type: text/plain; charset=iso-8859-1 Organization: Universite de Sherbrooke Message-Id: <1085684740.3286.4.camel@idefix.homelinux.org> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Thu, 27 May 2004 15:05:40 -0400 X-UdeS-MailScanner-Information: Veuillez consulter le http://www.usherbrooke.ca/vers/virus-courriel X-UdeS-MailScanner: Aucun code suspect =?ISO-8859-1?Q?d=E9tect=E9?= X-MailScanner-SpamCheck: n'est pas un polluriel, SpamAssassin (score=-4.9, requis 5, autolearn=not spam, BAYES_00 -4.90) X-MailScanner-From: jean-marc.valin@usherbrooke.ca X-MIME-Autoconverted: from 8bit to quoted-printable by smtpi1.usherbrooke.ca id i4RJ5euU017084 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id i4RJ60gi009522 X-archive-position: 236 X-ecartis-version: Ecartis v1.0.0 Sender: fam-bounce@oss.sgi.com Errors-to: fam-bounce@oss.sgi.com X-original-sender: Jean-Marc.Valin@USherbrooke.ca Precedence: bulk X-list: fam > It would be interesting if fam is monitoring the directory you are > working in. > Check > $ fuser -v /directory > or > $ lsof | grep /directory Yes, I see a bunch of things there: USER PID ACCESS COMMAND /home/jm/phd/jmvalin/overflow jm 3340 ..c.. zsh jm 3346 ..c.. batchflow jm 3347 ..c.. grep jm 3348 ..c.. grep > Your experience is backing my impression that file alteration monitoring > via events (kernel directory notification using dnotify) is less > efficient than people tend to expect... > > What you could try: > > to disable fam in xinetd > or > recompile fam without the dnotify patch. Actually, the main thing is that I don't think fam should ever be enabled by default on a system. Such unpredictable behaviour is simply not acceptable from a daemon. Jean-Marc -- Jean-Marc Valin http://www.xiph.org/~jm/ LABORIUS Université de Sherbrooke, Québec, Canada From amadorm@usm.edu.ec Mon May 31 10:45:13 2004 Received: with ECARTIS (v1.0.0; list fam); Mon, 31 May 2004 10:45:16 -0700 (PDT) Received: from mailman.eljuri.com (19.red-gye.satnet.net [200.63.196.19] (may be forged)) by oss.sgi.com (8.12.10/8.12.9) with SMTP id i4VHj9gi025125 for ; Mon, 31 May 2004 10:45:12 -0700 Received: from mailman.vanguardpublicidad.com (IDENT:root@[10.10.1.145]) by mailman.eljuri.com (8.10.2/8.10.2) with ESMTP id i4VGiPH01916; Mon, 31 May 2004 11:45:07 -0500 Received: from [10.10.25.111] ([10.10.25.111]) by mailman.vanguardpublicidad.com (8.10.2/8.10.2) with ESMTP id i4VH4OE24182; Mon, 31 May 2004 12:05:23 -0500 Subject: Re: fam using lots of CPU From: "Manuel Amador (Rudd-O)" To: Jean-Marc Valin Cc: nf2@scheinwelt.at, fam@oss.sgi.com, Nautilus mailing In-Reply-To: <1085684740.3286.4.camel@idefix.homelinux.org> References: <1085644229.3221.16.camel@idefix.homelinux.org> <1085683907.3438.54.camel@lilota.lamp.priv> <1085684740.3286.4.camel@idefix.homelinux.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-NPJ6W+D6oXoKpTmbtWEz" Message-Id: <1086025255.26460.19.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 (1.4.5-7) Date: Mon, 31 May 2004 12:40:55 -0500 X-archive-position: 237 X-ecartis-version: Ecartis v1.0.0 Sender: fam-bounce@oss.sgi.com Errors-to: fam-bounce@oss.sgi.com X-original-sender: amadorm@usm.edu.ec Precedence: bulk X-list: fam --=-NPJ6W+D6oXoKpTmbtWEz Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable El jue, 27-05-2004 a las 14:05, Jean-Marc Valin escribi=C3=B3: >=20 > Actually, the main thing is that I don't think fam should ever be > enabled by default on a system. Such unpredictable behaviour is simply > not acceptable from a daemon. Or maybe that fam should be enabled if it weren't that braindamaged when met with dnotify... >=20 > Jean-Marc >=20 > --=20 > Jean-Marc Valin > http://www.xiph.org/~jm/ > LABORIUS > Universit=C3=A9 de Sherbrooke, Qu=C3=A9bec, Canada --=20 Manuel Amador (Rudd-O) GPG key ID: 0xC1033CAD at keyserver.net --=-NPJ6W+D6oXoKpTmbtWEz Content-Type: application/pgp-signature; name=signature.asc Content-Description: Esta parte del mensaje =?ISO-8859-1?Q?est=E1?= firmada digitalmente -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQBAu24nWyznNMEDPK0RAkKDAJ41Ze6lFGfOb6E61201BB6b5sPqTACdEL4e 0aHJsPweTYpY0VhaV3VKcto= =bfmw -----END PGP SIGNATURE----- --=-NPJ6W+D6oXoKpTmbtWEz-- From innfo@aol.com Mon May 31 17:49:28 2004 Received: with ECARTIS (v1.0.0; list fam); Mon, 31 May 2004 17:49:30 -0700 (PDT) Received: from 61.255.55.8 (kejpcb@[61.255.55.8]) by oss.sgi.com (8.12.10/8.12.9) with SMTP id i510nDgi010903 for ; Mon, 31 May 2004 17:49:21 -0700 Message-Id: <200406010049.i510nDgi010903@oss.sgi.com> Received: from mail.ldlkm.com (mail.ldlkm.com [207.99.9.130]) by blv-smtpin-01.boeing.com with esmtp; éåðé, 01 2004 01:46:13 +0300 From: udelnet To: Undisclosed.Recipients@oss.sgi.com Subject: Mime-Version: 1.0 Content-Type: text/html; charset="iso-8859-8" Date: Tue, 1 Jun 2004 02:47:31 +0200 X-Mailer: AOL 7.0 for Windows US sub 118 X-archive-position: 239 X-ecartis-version: Ecartis v1.0.0 Sender: fam-bounce@oss.sgi.com Errors-to: fam-bounce@oss.sgi.com X-original-sender: innfo@aol.com Precedence: bulk X-list: fam Content-Length: 1518 Lines: 32 This is HTML source of message you composed. Do not modify here. To modify this message press HTML Messages Editor button.
 
 
notice: This is a one time message. You have received this e-mail because you expressed interest in career and employment information. in case you suppose this mail has reached your mailbox by an error, we certainly apologize.
 
 
????: ???? ?? ???? ???? ???? ?????????? ????? ?????????? ???? ?????. ????? ????? ???? ????? ?? ???? ?? ???? ????? ??? ?????, ??? ??????? ???? - ???? ????? ?? ?????. ?? ???? ??????? ????? ?????? ??????, ??? ??? ???.