Debian Bug report logs - #859265
ltsp-build-client: exim4-configuration fails because /opt/ltsp/amd64 is not world-readable

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: q9 <qqqqqqqqq9@gmeyer.df-kunde.de>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: ltsp-build-client: exim4-configuration fails because /opt/ltsp/amd64 is not world-readable

Date: Sat, 01 Apr 2017 15:05:53 +0200

Package: ltsp-server-standalone
Version: 5.5.9-2
Severity: important

Dear Maintainer,

   * What exactly did you do (or not do) that was effective (or
     ineffective)?
I ran 
    ltsp-build-client --copy-sourceslist --purge-chroot 

   * What was the outcome of this action?
The CHROOT-Generation failed because the exim4-configuration failed.
The error message was: user mail was not found

I was able to circumvent the problem by forcing /opt/ltsp/amd64 to be world-readable

chmod 755 /opt/ltsp
(sleep 15 ; chmod 755 /opt/ltsp/amd64 ) & ltsp-build-client --copy-sourceslist --purge-chroot
 

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages ltsp-server-standalone depends on:
ii  dnsmasq                               2.76-5
ii  gnome-session [x-session-manager]     3.22.3-1
ii  gnupg                                 2.1.18-6
ii  kwin-x11 [x-window-manager]           4:5.8.6-1
ii  ldm-server                            2:2.2.18-2
ii  libasound2-plugins                    1.1.1-1
ii  ltsp-server                           5.5.9-2
ii  ltspfs                                1.4-2+b1
ii  mutter [x-window-manager]             3.22.3-2
ii  nbd-server                            1:3.15.2-2
ii  openbsd-inetd [inet-superserver]      0.20160825-2
ii  openssh-server                        1:7.4p1-9
ii  plasma-workspace [x-session-manager]  4:5.8.6-2
ii  squashfs-tools                        1:4.3-3+b1
ii  x11-utils                             7.7+3+b1
ii  xauth                                 1:1.0.9-1+b2

Versions of packages ltsp-server-standalone recommends:
ii  ltsp-docs  1.2-1

ltsp-server-standalone suggests no packages.

-- no debconf information

Message #10 received at 859265@bugs.debian.org (full text, mbox, reply):

From: q9 <qqqqqqqqq9@gmeyer.df-kunde.de>

To: 859265@bugs.debian.org

Subject: Problem due to wrong umask

Date: Sat, 1 Apr 2017 15:17:54 +0200

Just after sending, I realized the problem ist due to my root umasl being 077. Sorry for the noise.

Message #15 received at 859265-done@bugs.debian.org (full text, mbox, reply):

From: Vagrant Cascadian <vagrant@debian.org>

To: 859265-done@bugs.debian.org

Subject: Re: Bug#859265: ltsp-build-client: exim4-configuration fails because /opt/ltsp/amd64 is not world-readable

Date: Thu, 14 Sep 2017 11:49:29 -0700

[Message part 1 (text/plain, inline)]

On 2017-04-01, q9 wrote:
>     ltsp-build-client --copy-sourceslist --purge-chroot 
>
>    * What was the outcome of this action?
> The CHROOT-Generation failed because the exim4-configuration failed.
> The error message was: user mail was not found
>
> I was able to circumvent the problem by forcing /opt/ltsp/amd64 to be world-readable
>
> chmod 755 /opt/ltsp
> (sleep 15 ; chmod 755 /opt/ltsp/amd64 ) & ltsp-build-client --copy-sourceslist --purge-chroot

Since your umask was set very restrictively, this is a bit of an unusual
configuration, and I'm not sure there's anything LTSP can do to fix
this.

If it were to ignore or reset your umask, that could cause other more
severe problems, as you've clearly requested the umask for a reason.

Marking as done for now.


live well,
  vagrant

[signature.asc (application/pgp-signature, inline)]

Send a report that this bug log contains spam.