For the list. A safe way to update a large deployment, is to back up the config file, reinstall from scratch. Then convert the config file and place it back into flowvisor's install tree.
Note that this only applies to people installing from binary. Cheers. -- Ali On Jun 4, 2012, at 9:15 AM, Josh Smift wrote: > JBS> Mm, ok. At BBN in particular, we currently run our FlowVisors as a > JBS> user named 'openflow', so it's not either (a) root; or (b) some > JBS> random person on the system; but it's not named 'flowvisor' either. > > AA> Ah I was worried about this. I was under the impression that people > AA> who install from binary run flowvisor as a specific user (which I > AA> thought was flowvisor). I'll see if I can fix this. > > Yeah, it has been; we were running it as 'openflow' before that change, > and have been modifying the init.d file after installing. :^/ It'd be > nice to get back in synch about this. > > JBS> (Also, "flowvisor" is more than eight characters, which probably > JBS> won't cause obvious problems on modern Linux systems, but will almost > JBS> certainly cause subtle problems at some point when you least expect > JBS> it. :^( Is that actually hardcoded in?) > > AA> well all the flowvisor db files are owned by user flowvisor... > > Sure, but that might just be a quick chown. > > AA> Sorry about all this, I am by far no apt expert. I'll try to figure > AA> out how to make this a smoother process. > > No worries. We can also talk more about it off-list, since most > openflow-discuss people may not be all that interested in this level of > detail. :^) > > -Josh (j...@bbn.com) > _______________________________________________ > openflow-discuss mailing list > openflow-discuss@lists.stanford.edu > https://mailman.stanford.edu/mailman/listinfo/openflow-discuss _______________________________________________ openflow-discuss mailing list openflow-discuss@lists.stanford.edu https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
