Skip to content

WATCHMAN_SOCK not respected by spawned service #1277

@nekowinston

Description

@nekowinston

Problem

Running WATCHMAN_SOCK=/tmp/watchman.sock watchman spawns a service with a service inside <STATEDIR>/<USER>, when I would expect the environment variable to act like the command line flag --unix-listener-path=/tmp/watchman.sock.

When supplying both

WATCHMAN_SOCK=/tmp/watchman.sock watchman --unix-listener-path=/tmp/foo.sock

I would expect the command line flag to take precedence.

Motivation

I'd like to define WATCHMAN_SOCK once inside my environment variables to

  • have watchman respect that value when spawning the service for me
  • have other services that query Watchman know which socket to call, instead of having to spawn watchman get-sockname on each invocation, or once and then caching the result somehow.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions