Hi I have been using Sedna for some time now, but recently began noticing some strange behaviour. Unfortunately I cannot confirm whether this was actually happening form the start or not. Before I go into the details of the problem, I would like to clarify something.
I run Sedna on two computers - one runs 64-bit Fedora 7 (8GB RAM) and the other 32-bit Ubuntu 8.04 (2GB RAM). I began monitoring memory use of various processes recently (via the Linux "top" command) and I noticed a difference in se_sm behaviour between the two computers: when I run se_sm <db_name> on 64-bit Fedora I get 5 se_sm processes in the memory, each taking up the same amount of memory, whereas on 32-bit Ubuntu I only get one instance of se_sm in the memory. I tried this with several databases. In both cases all se_sm instances go away when se_smsd is called on the relevant database. I was wondering if any of this is expected behaviour? ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Sedna-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sedna-discussion
