NSD 2.3.2 error at nsdc.sh.in

Robert Martin-Legene robert at dk-hostmaster.dk
Mon Dec 5 12:41:34 UTC 2005

On Mon, Dec 05, 2005 at 12:20:44PM +0100, Miek Gieben wrote:
> -        (umask 222; echo "database locked bij PID: $$") >${lockfile}) ||
> +        ((umask 222; echo "database locked bij PID: $$") >${lockfile}) ||

I'm curious.. What's the point of setting the umask before echoing
something? The way I see it the $lockfile is created by the "parent"
(i.e. not by the subshell)?

And if the umask 222 would work, would the file ever have more than 0
octets in it? As I see it, the file would be created so the shell can't
write to it.

-- robert
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 185 bytes
Desc: not available
URL: <http://lists.nlnetlabs.nl/pipermail/nsd-users/attachments/20051205/0759df89/attachment.bin>

More information about the nsd-users mailing list