So if you do not have openoffice installed it does not happen? On (20/12/06 08:42), Ian Darwin wrote: > If you have OOo installed and build it again, it seems to try to write > into there, at least that's what this looks like when building with > systrace. Mind, I've just started running with systrace so please let > me know if this is normal "idle chit-chat". > > systrace: deny user: ian, prog: > /usr/ports/editors/openoffice/w-openoffice-2.1.0p1-no_lang/OOE680_m6/solver/680/unxobsd.pro/bin/idlc, > > pid: 32026(0)[8333], policy: /usr/bin/make, filters: 193, syscall: > native-fswrite(136), filename: /usr > systrace: deny user: ian, prog: > /usr/ports/editors/openoffice/w-openoffice-2.1.0p1-no_lang/OOE680_m6/solver/680/unxobsd.pro/bin/idlc, > > pid: 32026(0)[8333], policy: /usr/bin/make, filters: 193, syscall: > native-fswrite(136), filename: /usr/ports > systrace: deny user: ian, prog: > /usr/ports/editors/openoffice/w-openoffice-2.1.0p1-no_lang/OOE680_m6/solver/680/unxobsd.pro/bin/idlc, > > pid: 32026(0)[8333], policy: /usr/bin/make, filters: 193, syscall: > native-fswrite(136), filename: /usr/ports/editors > systrace: deny user: ian, prog: > /usr/ports/editors/openoffice/w-openoffice-2.1.0p1-no_lang/OOE680_m6/solver/680/unxobsd.pro/bin/idlc, > > pid: 32026(0)[8333], policy: /usr/bin/make, filters: 193, syscall: > native-fswrite(136), filename: /usr/ports/editors/openoffice > > Is Sun's idlc actually trying to open /usr for writing? > > Also, after printing about 3,000 of these failures, it reports "IDLC > Successful"... nice definition of "success". Interested parties may > inquire of me in a couple of days to see if the port otherwise finished > building successfully :-)
