Thanks for the reply. I used pip to install mailman

On Tue, Aug 15, 2017 at 10:59 PM, Abhilash Raj <maxking@asynchronous.in> wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256

On Tue, 15 Aug 2017 18:45:14 -0400 Leon <best.sum@gmail.com> wrote:

...

Hello, I wonder if this issue(https://gitlab.com/ mailman/mailman/issues/3) was fixed?

It was fixed actually, but it might be a problem when the files aren't installed int the bin directory specified in the configuration.

...

I try to set up a mailing list on aws ec2(ubuntu). In the instruction( http://docs.mailman3.org/en/latest/prodsetup.html), it doesn't require to install mailman in a virtual env. However, when I tried to run mailman start, it produces /usr/bin/python3: can't open file '/usr/bin/master': [Errno 2] No such file or directory.

Can you show us the contents of mailman.cfg that you are using?

[paths.custom] var_dir: /home/ubuntu/mailman bin_dir: /sbin queue_dir: /var/spool/mailman log_dir: /var/log/mailman lock_dir: /var/lock/mailman etc_dir: /etc ext_dir: /etc/mailman.d pid_file: /var/run/mailman/master.pid

[mailman] layout: custom

Exception: /usr/bin/python3: can't open file '/sbin/master': [Errno 2] No such file or directory

If you are using [paths.fhs], then I guess I can imagine why this is a problem.

@Barry: Is is wrong for the [paths.fhs] to set the bin_dir? No other paths configuration does this.

When you install using any tool like pip, the console scripts usually land in /usr/local/bin or /usr/bin depending on the distro, but using the [paths.fhs] doesn't work in these cases because the scripts are not in /sbin and hence the error as presented above.

thanks, Abhilash Raj

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEVB6gRIRTOU/3eg7MnZsroGHQpnwFAlmTtRwACgkQnZsroGHQ pnzP+RAAjP1IxSxYoRUrmdm3QMvp1JuL1vbT+zt+j3uiRucMMfpPvWm6l1gbbMCH jWUgAkB8ABWzRLCNLz6jaH1aWfR9PDfEL3oJkcEsXe2yBf9Pho1SlsqdqxAPLMND L8HGowuxXLnXihcLw1MQnwAPwQLZxK5dYhaD2TsNB2TCsuMK/AxS4mwUqkAmNcBd uhAlIKXhy7SAGP8qbEvyxZd+DC3KEvFDc6thNuAg56fC0NYit7buU/vCS8M30Tpu niu/aP4kvDy5reSZMX0jy6wiavDm3nIDJwnMYb6TIwfVyYRqP7cQfNcLJy2Wd1sq GVRBM3pE0qKil1p/v/ebzs8WdZAUPXrmWL/8ZCbkcLcojY1Tuv0D9m4zu+MmBCPB dpm5hZ046P2jWIa0OgmHzazu3riGRSv7kjCW3HO+IynHzt3ZCAhc5lzOzAt3z99i EOp99CnMrcZ8BLD334CMl5nRScBvhZM369ucUVhrSjeu2sX4oTzFosV8DuCp82FV WJ9Oh2e1hQa/u4j+6OQZqaV9eNEFRkKXhr6VcfLbVzdWzm5VxM0zprlCFfRjJDz7 FN2+PTADSHXOiZkTiggZ2K+PuC4q6f4GRyGCNwVocH6d3mGbAIvIY4+oOoVArjje r9qbHU+0kgeKrNVer9Q0MYaE2H38rKsqep6TUzNN5ltYJLKh1XI= =q8m2 -----END PGP SIGNATURE-----

-- Best wishes, Leon

On Aug 15, 2017, at 19:59, Abhilash Raj <maxking@asynchronous.in> wrote:

@Barry: Is is wrong for the [paths.fhs] to set the bin_dir? No other paths configuration does this.

All the other path configs calculate their bin_dir based on sys.executable. In config.py:

    default_bin_dir = os.path.abspath(os.path.dirname(sys.executable))
…
substitutions = dict(
    …
    argv=default_bin_dir,

and from schema.cfg:

# This is the directory containing the Mailman 'runner' and 'master' commands # if set to the string '$argv', it will be taken as the directory containing # the 'mailman' command. bin_dir: $argv

However, I think for paths.fhs, it is correct to hardcode bin_dir to /sbin (although perhaps it should be /usr/sbin now).

http://www.pathname.com/fhs/pub/fhs-2.3.html#SBINSYSTEMBINARIES

paths.fhs very specifically expects things to be laid out according to the FHS.

-Barry