[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#292377: apache-perl: umask again

Package: apache-perl
Version: 1.3.33-2
Severity: normal

This is probably related to #167966 (archived)

In my experience apache-perl inherits its umask from process, invoking

Our web application creates session files. Our nightly maintenance
cronjobs use /etc/init.d/apache-perl to stop/start apache. Also, the
cronjobs sets umask 0227 (having in mind permissions of archived files).
In the morning, the session files created are with access rights
r--r-----, which effectifely disables any writing to them.

In #167966 I see a reference to /etc/init.d/rcS, which indeed sets umask
0022. However, /etc/init.d/apache-perl never sources /etc/init.d/rcS.

Maybe /etc/init.d/apache-perl should a) source /etc/init.d/rcS, or b)
set a saner umask itself, or c) document the issue in README.Debian.

Thank you for your attention.

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8
Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8)

Versions of packages apache-perl depends on:
ii  apache-common               1.3.33-2     Support files for all Apache webse
ii  debconf                     1.4.42       Debian configuration management sy
ii  dpkg                        1.10.26      Package maintenance system for Deb
ii  libapache-mod-perl  Integration of perl with the Apach
ii  libc6                       2.3.2.ds1-20 GNU C Library: Shared libraries an
ii  libdb4.2                    4.2.52-17    Berkeley v4.2 Database Libraries [
ii  libexpat1                   1.95.8-1     XML parsing C library - runtime li
ii  libmagic1                   4.12-1       File type determination library us
ii  libperl5.8                  5.8.4-5      Shared Perl library
ii  logrotate                   3.7-2        Log rotation utility
ii  mime-support                3.28-1       MIME files 'mime.types' & 'mailcap

-- debconf information excluded

Reply to: