Re: [Virtuoso-users] Virtuoso AMI; Data Lifecycle and Persistence WRT AMI lifecycle; Best Practices

2008-12-03 Thread Kingsley Idehen
Aldo Bucchi wrote: Kingsley, On Wed, Dec 3, 2008 at 11:52 AM, Kingsley Idehen wrote: Aldo Bucchi wrote: Hi All, = About Data and State = Using any of the Virtuoso Universal Sever AMIs for Amazon EC2, what are the recommended guidelines for persistence? I can see that you suggest cre

Re: [Virtuoso-users] Virtuoso AMI; Data Lifecycle and Persistence WRT AMI lifecycle; Best Practices

2008-12-03 Thread Aldo Bucchi
Kingsley, On Wed, Dec 3, 2008 at 11:52 AM, Kingsley Idehen wrote: > Aldo Bucchi wrote: >> >> Hi All, >> >> = About Data and State = >> >> Using any of the Virtuoso Universal Sever AMIs for Amazon EC2, what >> are the recommended guidelines for persistence? >> I can see that you suggest creating a

Re: [Virtuoso-users] Virtuoso AMI; Data Lifecycle and Persistence WRT AMI lifecycle; Best Practices

2008-12-03 Thread Kingsley Idehen
Aldo Bucchi wrote: Hi All, = About Data and State = Using any of the Virtuoso Universal Sever AMIs for Amazon EC2, what are the recommended guidelines for persistence? I can see that you suggest creating an S3 account ( but there's no further touching on the topic ), which brings me to the foll

[Virtuoso-users] Virtuoso AMI; Data Lifecycle and Persistence WRT AMI lifecycle; Best Practices

2008-12-03 Thread Aldo Bucchi
Hi All, = About Data and State = Using any of the Virtuoso Universal Sever AMIs for Amazon EC2, what are the recommended guidelines for persistence? I can see that you suggest creating an S3 account ( but there's no further touching on the topic ), which brings me to the following set of question

Re: [Virtuoso-users] Setup Virtuoso 5.0.9

2008-12-03 Thread Robert Jones
3/12/08 7:31 AM, "Kingsley Idehen" : > Till Plumbaum wrote: >> >> I already installed and tested virtuoso open source edition 5.0.9 on >> my local machine and everything worked fine. But when I try to connect >> to the Conductor Interface or the database (both running on the >> default port) fro