Hey guys, I'm trying to dump a recent planet.osm file to a local PostgreSQL database on OS X. I'm running a 120 GB SSD for my system drive, and a 500GB 7200RPM external drive for the database connected via Firewire 800. When I run osmosis with a simple read-xml, write-pgsql command I notice my system drive (the SSD) in activity manager fills up while my database (on the 500GB external drive) isn't being populated at all, or used at all. It's on this step: `Processing input data, building geometries and creating database load files.` Obviously the SSD isn't large enough to handle whatever operations are being cached / created. So my question is, what is osmosis creating in the background and is there a way to force it to utilize the other volume instead of the system default? After some testing, I believe that Osmosis is utilizing the temp folder on OS X, which is why I am seeing drive usage on my system drive/my SSD. I am unsure if I can relocated the temp folder or if Java / Osmosis can told made to use another directory. THANKS! -Cody

Hey guys, I'm trying to dump a recent planet.osm file to a local PostgreSQL database on OS X. I'm running a 120 GB SSD for my system drive, and a 500GB 7200RPM external drive for the database connected via Firewire 800. When I run osmosis with a simple read-xml, write-pgsql command I notice my system drive (the SSD) in activity manager fills up while my database (on the 500GB external drive) isn't being populated at all, or used at all. It's on this step: `Processing input data, building geometries and creating database load files.` Obviously the SSD isn't large enough to handle whatever operations are being cached / created. So my question is, what is osmosis creating in the background and is there a way to force it to utilize the other volume instead of the system default? THANKS! -Cody

Hey guys, I'm trying to dump a recent planet.osm file to a local PostgreSQL database on OS X. I'm running a 120 GB SSD for my system drive, and a 500GB 7200RPM external drive for the database connected via Firewire 800. When I run osmosis with a simple read-xml, write-pgsql command I notice my system drive (the SSD) in activity manager fills up while my database (on the 500GB external drive) isn't being populated at all, or used at all. Obviously the SSD isn't large enough to handle whatever operations are being cached / created. So my question is, what is osmosis creating in the background and is there a way to force it to utilize the other volume instead of the system default? THANKS! -Cody

Hey guys, I'm trying to dump a recent planet.osm file to a local PostgreSQL database on OS X. I'm running a 120 GB SSD for my system drive, and a 500GB 7200RPM external drive for the database connected via Firewire 800. When I run osmosis with a simple read-xml, write-pgsql command I notice my system drive (the SSD) in activity manager fills up while my database (on the 500GB external drive) isn't being populated at all, or used at all. Obviously the SSD isn't large enough to handle whatever operations are being cached / created. So my question is, what is osmosis creating in the background and is there a way to force it to utilize the other volume instead of the system default? THANKS! -Cody