🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.protocols.iso.dev-environ
Article #520

program specific tailoring

#520
From: Hans Eriksson
Date: Mon, 18 Mar 1991 13:59
27 lines
1471 bytes
I have been struggling with this feature but cannot get it to work as
I think it should.

I am trying to enable "all" debuging for a specific program. If add
"all" to the default isotailor file and place it in the $ETCDIR
everythings works fine, ie there is a LOT of logging onto the
terminal.

But I do not want that for all my ISODE programs, just for the
presumed buggy ones. So far I have tried every combination of
programname_tailor placed in my home-dir, in the current-dir etc, but
I cannot get it to log!

The scenario:
	I have a ROS initiator called "lookup".
	I have a ROS responder called "ros.kilroy00"
	They are all placed in my dir /home/shino/hans/kilroy
	My home-dir is /home/shino/hans

To enable logging just for my initiator, where should I place the
tailor-file and what should I call it? /home/shino/hans/.lookup_tailor
?? does not work According to ls -lu, the file does not even get
touched. I have removed the $ETCDIR/isotailor just in case.

For this exercise, it is still 6.0.

/hans
Technical Details
Message-ID: <9103181359.AA08688@shino.sics.se>
Path: arc1-ca.pugleaf.net!utzoo!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!SICS.SE!hans

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!SICS.SE!hans
From: hans@SICS.SE (Hans Eriksson)
Newsgroups: comp.protocols.iso.dev-environ
Subject: program specific tailoring
Message-ID: <9103181359.AA08688@shino.sics.se>
Date: 18 Mar 91 13:59:03 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: inet
Organization: The Internet
Lines: 27