Email Detail

HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "url": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/3RWFFWUTKJ73C6ESFCV64MGLBFR7JH3F/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "3RWFFWUTKJ73C6ESFCV64MGLBFR7JH3F",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/EEYQAVUP3ZTVDSOAHREESCO4ZEZVT2EN/?format=api",
    "sender": {
        "address": "eric.fort (a) gmail.com",
        "mailman_id": "2b2633ba6515405baf7680ea3c20a9ef",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/2b2633ba6515405baf7680ea3c20a9ef/emails/?format=api"
    },
    "sender_name": "Eric Fort",
    "subject": "[amsat-bb] Re: predict -s starts then immediately crashes",
    "date": "2009-04-14T10:16:40Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/FGG5JJLLV73SCZQK27IDEQSUE6AOURKN/?format=api",
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "/etc/services still seems to require a proper entry for whatever port number\nyou may specify predict to run as.  Without that entry associating predict\nwith that port number, predict crashes.  one thing I had to fix was\n/etc/services had port 1210 udp assigned to another service.  predict\nrepeatedly crashed until I specified in /etc/services an association between\npredict and the port it wanted to run on, replacing the service that was\nformerly bound to said port (1210).\n\nEric\nAF6EP\n\nOn Mon, Apr 13, 2009 at 11:45 PM, Xavi EB3CZS <[email protected]> wrote:\n\n> Also, if you can't/don't want to change the file /etc/services, you can\n> invoke predict as\n>\n> predict -s -n 1210\n>\n> note that you can change the 1210 (port number) to whatever you like most,\n> and that you can have multiple predict servers running on the same machine\n> listening on different ports. So maybe you can have the amateur sats on one\n> server, weather sats on another server, etc.\n>\n> 73 de Xavi EB3CZS\n>\n> On Sun, Apr 12, 2009 at 2:08 PM, Eric Fort <[email protected]> wrote:\n>\n>> under debian predict runs setup like it should then terminates never\n>> getting\n>> to the multi satelite screen.  on running it again it starts over in\n>> setting\n>> up the qth, even though ~/.predict/predict.qth is present.\n>>\n>> just fixed the problem:\n>>\n>> the following 3 files seem to need to be present for predict to run:\n>>\n>> ~/.predict/predict.qth\n>> ~/.predict/predict.db\n>> _/.predict/predict.tle\n>>\n>> to run as a server /etc/ services must have port 1210/udp assigned to\n>> predict.\n>>\n>> my osx install also now runs the predict server.  osx assigns aborher\n>> service to port 1210 by default.\n>>\n>> noww both work.\n>>\n>> Eric\n>> AF6EP\n>>\n>> On Sun, Apr 12, 2009 at 3:01 AM, Eric Fort <[email protected]> wrote:\n>>\n>> > predict -s (pedict invoked as a server) immediately crashes (terminates)\n>> > after startup.  anyone have an idea why it would do this?  (works fine\n>> when\n>> > not invoked as a server)\n>> >\n>> > Thanks,\n>> >\n>> > Eric\n>> > AF6EP\n>> >\n>> >\n>> >\n>> _______________________________________________\n>> Sent via [email protected]. Opinions expressed are those of the author.\n>> Not an AMSAT-NA member? Join now to support the amateur satellite program!\n>> Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb\n>>\n>\n>\n>\n> --\n> 73 de Xavi EB3CZS\n>\n",
    "attachments": []
}