Fix cygwin's GNU screen /tmp/uscreens permission errors

Note: The latest Cygwin release of screen works fine now.

The current (e.g., 4.3.1) GNU screen command generally fails to work correctly on cygwin due to directory permission checks - for example, on /tmp/uscreens. To remedy this problem, you can run mkpasswd / mkgroup for every Windows user that runs cygwin. But this isn't foolproof because /tmp can easily become unusable by screen. Or you can modify screen and avoid the checks entirely. Here's how.

1. Run cygwin's setup program and install:

Source for the screen package
gcc
libncurses-devel

2. After installing, run the cygwin prompt
3. cd /usr/src
4. tar -xzf screen*.gz
5. cd screen-*
6. ./configure
7. Edit Makefile

change the line ETCSCREENRC = to ETCSCREENRC = /etc/screenrc

8. Edit screen.c. See [1] for more details. Remove the statements that start with:

if (((int)st.st_mode & 0777) != n) ...
if ((st.st_mode & 0777) != 0700) ...
if ((int)st.st_uid != real_uid)
if ((int)st.st_uid != multi_uid)

9. make

10. cp screen /bin

[1] https://gist.github.com/pasela/3401354

Comments

Running 2560x1080 on LG 29UM57-P on an old MacBook Pro OSX El Capitan

Yes. A mid-2011 MacBook Pro running OSX El Capitan can drive a 2560x1080 monitor via HDMI.
I was not able to get 60 Hz working. I am settling with 53 Hz. I tried many settings before finding something that works. The refresh rate seems fine to me. Maybe the text could be clearer but for a $200 monitor running this resolution, I'll take it. Apple MacBook 2015 retina resolution is 2560 x 1800. Consider buying a better monitor that may literally give you fewer headaches. Install SwitchResXFollow the instructions for disabling SIPAfter rebooting, run SwitchResX via System PreferencesSelect your LG monitorClick Custom ResolutionsClick the + icon Enter these settings (source)Exit SwitchResX and saveRebootRun SwitchResX via System PreferencesSelect your LG monitorClick Current ResolutionsSelect the 2560x1080, 53 Hz settingEnable SIPIf you discover better settings, please leave a comment.

Collecting and graphing metrics via Apache Camel, Statsd, and Graphite

If you're curious about Apache Camel's metrics reporting via Dropwizard, this guide will help you get Graphite running in a Docker container. Then you will run an instrumented Camel application and view its metrics via Graphite's browser UI.

(1) Install Docker

There are many ways to do this depending on your platform. Google it.

(2) Install and run the Docker container for Statsd and Graphite

Refer to https://github.com/hopsoft/docker-graphite-statsd

The instructions infer that you can run the container without specifying port mappings. This is plain wrong. So use the following command to start the container:

docker run -d --name graphite --restart=always -p 80:80 -p 8125:8125/udp hopsoft/graphite-statsd It is not necessary to enable Graphite's UDP listener. Statsd receives metrics via UDP and forwards them to Graphite over TCP. (3) On Windows and OSX, determine the IP address of the graphite Docker container

On Linux, you can use localhost.

On Windows and OSX, there are…

As California Burns

For the past week, San Franciscans have been wearing respirators to protect their lungs from California's burned carcass in the sky.

Some of the particulates were once human flesh and expensive multi-story homes. Some were paint, pesticides, car batteries, and insulation.

One in five people are wearing masks matter-of-factly. No hysterics. No protests. No mention of the motherfuckers who brought catastrophic runaway climatic heating to our state, burning Californians alive without any warning.

What will Kamala Harris and Dianne Feinstein do after the cadaver dogs leave Paradise? They'll do the same as Repiglicans. They'll do what they've done their entire careers. They will say and do nothing to save us. That’s why they’re senators.

Void Where Prohibited

Search This Blog