[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20050125174123.GC11835@openwall.com>
Date: Tue, 25 Jan 2005 20:41:23 +0300
From: Solar Designer <solar@...nwall.com>
To: owl-users@...ts.openwall.com
Subject: Re: rpm warning and openwall temporary file handling
On Tue, Jan 25, 2005 at 11:22:01AM +0700, Ihsan wrote:
> After upgrade to latest Owl-current I found that rpm compilation produce
> many warnings like this: "--march depraceted, use --mtune or --march
> instead".
Please make sure you update _all_ of Owl to the latest. You might
have copied the .rpm* files in ~build from an older native tree, --
you need to reset these to be symlinks to under the new native tree
instead ("rm .rpm* && make symlinks"). The problem will go away.
> And I found also problem that I think related to temporary file
> handling on Owl. For example on mysql server (4.1.x) dan clamd antivirus daemon,
> the daemon fail to start with error message like: "Access denied on
> /tmp/.private/root/....."
Yes, this is an instance of a fairly generic problem with the approach
we use for per-user temporary file directories. If a process switches
to a different user ID, its TMPDIR setting might no longer be correct.
The problem typically shows up when you start a daemon manually
(rather than let it get started on system bootup).
For daemons which are a part of Owl and for those which use Red Hat
style startup scripts (hint!), we've addressed this problem in the
daemon() function (in /etc/init.d/functions) by not exporting TMPDIR
into the daemon being started.
The per-user temporary file directories are thus only for users' (and
root-privileged administrators') sessions to the servers, not for
system daemons.
--
Alexander Peslyak <solar at openwall.com>
GPG key ID: B35D3598 fp: 6429 0D7E F130 C13E C929 6447 73C3 A290 B35D 3598
http://www.openwall.com - bringing security into open computing environments
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
