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

Bug#1894: install syslogd and /var/logs/nes



Erick Branderhorst writes ("Bug#1894: install syslogd and /var/logs/nes"):
> Setting up syslogd ...
> mkdir: cannot make directory `/var/logs/news': No such file or directory
>                                       ~
> chmod: /var/logs/news: No such file or directory
> chown: /var/logs/news: No such file or directory
> /var/lib/dpkg/info/syslogd.postinst: /var/lib/dpkg/info/syslogd.postinst: line 29: syntax error: unexpected end of file
> dpkg: error processing syslogd (--install):
>  subprocess post-installation script returned error exit status 2

There are two bugs here, of course: firstly the wrong pathname, and
secondly the failure to use `set -e' to ensure that the script detects
errors and stops.

ALMOST ALL SH SCRIPTS SHOULD USE `set -e' OR EXPLICTLY TEST $? AFTER
*EVERY* COMMAND.

Does anyone fancy going through all our postinst sh scripts and
reporting as bugs any which could fail to notice a non-zero exit
status from one of the commands they run ?

Ian.


Reply to: