Hi Thomas, one warning note, MICO's documentation is unfortunately completely outdated. The most recent I know about is either source code or if you prefer book form Distributed Systems Architecture: A Middleware Approach by Arno Puder, Kay Roemer, Frank Pilhofer (all former MICO developers).
Anyway, please keep in mind that once you set something in .micorc, then it's used by all the MICO applications, i.e. client, servers, micod, imr etc. That's why for some apps you need to disable .micorc usage by pointing MICORC env var to nonexistent file... Cheers, Karel Schmidt Thomas wrote: > Hi, > > running an example like this given in Mico documentation (V 2.3.13) page > 38 will not complete daemon start up. (micod(8) does neither write its > IOR nor is the IMR accessible using imr(1)). My ".micorc" looks like > follows: > > -ORBNoResolve > -ORBImplRepoAddr inet:192.168.1.9:16001 > # We've explicitly tell our apps to bind to the IMR even when just > giving '-ORBImplRepoAddr' > -ORBBindAddr inet:192.168.1.9:16001 > #-ORBNamingAddr inet:192.168.1.9:16003 > -ORBIfaceRepoAddr inet:192.168.1.9:16005 > > Things will only work when setting the (undocumented) environment > variable MICORC to "/dev/null" as I've seen in some examples/demos. > > > -- > Thomas Schmidt > Schneiderstr. 16 > D-29575 Altenmedingen > Phone: +49-5807-209976 > Cellular: +49-172-3011505 > Skype: ThCSchmidt > Email: 01723011...@vodafone.de > PGP: Key-ID: 0x810B6206 > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Mico-devel mailing list > Mico-devel@mico.org > http://www.mico.org/mailman/listinfo/mico-devel -- Karel Gardas kgar...@objectsecurity.com ObjectSecurity Ltd. http://www.objectsecurity.com _______________________________________________ Mico-devel mailing list Mico-devel@mico.org http://www.mico.org/mailman/listinfo/mico-devel
