elkelk's questions

I'm working on a project that uses the custom Yodeck image on a raspberry pi 3. I need to install some additional software on the box and they provide a username and password for console login. After booting I can drop to a login prompt with ctrl+alt+F2. At the prompt, I can enter the username and password, but the password is ~120 character hash and I can only enter about 70 characters before hitting a 60-second login timeout.

Is there any way to deliver the password to the prompt in a fast enough way to beat the timeout (other than memorizing and typing like crazy)? I'm also open to ideas for increasing the timeout. It sounds trivial, but after several attempts, it appears to be too short of a time to login in a repeatable manner.

I've setup and tested celery on my amazon linux server, using mysql as the messaging backend and it works fine when running the program directly. My python project and celery install are located in a virtualenv. However if I attempt to daemonize celery by using the script here, the program refuses to run in the background.

I'm passing the virtualenv installed location of celery to the daemon in the config file using CELERYD="/opt/apps/myenv/[path to celeryd]" which equates to using the flag --cmd when starting celeryd.

The script always stops after starting worker node 1 and waits, as if I'm running the program directly and not daemonizing it. Celery is active at this point but stops after I close the terminal window or press ctrl-c.

I've tried running it without the --cmd, and it seems to run in the background, but the workers won't start, and calling stop returns an 'unknown instance'.

Any suggestions would be appreciated.

I am attempting to connect to a server via PHP fsockopen to initially get a cookie for basic auth and then to persistently connect to a streaming server defined in the Location header of the response.

The problem is that my code freezes on fgets and never receives any response data from the destination server. I'm connecting via https on port 443 on an Amazon ec2 instance. The server connects fine via curl in my server's terminal or via my chome browser.

Is there an outbound firewall setting that I'm missing on ec2? I've even opened up the inbound 443 port on the server, but of course that seems pointless.

Any thoughts?