Posted by joegml on April 27, 2009 at 9:18pm
I'm trying to talk to a Princeton B1000 broadcast server with a Linux system. It is acting coyly and doesn't want to play. The B1000 appears to be a locked Linux box.
Princeton server gui stats say that ssh is running on B1000, but when I try to log in via ssh, after establishing the ssh login dialogue (RSA key fingerprint, etc.) I get locked out with "This account is currently not available." rather than the standard denial. Princeton won't give us root on the box, which I understand, but it shouldn't be too much to ask to log in and copy files as a Linux user. Am I asking too much? Is this easy? Telvue support hasn't gotten back to me.
Advice appreciated.
Thanx.
Comments
Re: Does Televue (Princeton) Play Nice?
What info are you trying to get out of the Princeton?
Schedule info and some content metadata info is available via RSS feed or XML.
Info on Video files stored on the Priceton are available via the samba share.
we (Access Humboldt) have stitched together everything we need to automate the upload of shows from the Princeton to archive.org without having access to the contents of their mysql database.
I agree that it would be nice to have read-only access to it. i've considered booting the Princeton from a USB CD drive, and taking an archival copy of the non-media file systems. I've resisted the impulse so far...
Princetons have always had
Princetons have always had their OS locked down and with the 3.5 update, users have even less access. We used to be able to see the OS logs with a webmin interface, but now we are locked out of that as well.
We go back and forth about on how we feel about this at DOM. On one hand, Princeton has more API's than any other server we've worked with. From that perspective they are really open. On the other hand, Synergy users have full control of their Access database and can write their own APIs... but that's the only API's they'll get. It would be great if there was a better balance between access and APIs on Princetons, but it's hard to complain when they've added everything we've asked for to their APIs.
It certainly would have made our lives much easier to have direct access to the MySQL database vs. just the RSS feed form the Princeton. The upside of not having access to that is that our code is now playback agnostic using RSS to synchronize the MySQL or Access database in Drupal.
Princeton questions
For purposes of the ACM presentation next week, has anything changed above re: Princeton?