NetBSD-Bugs archive

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

Re: bin/57952 (dhcpcd(8) inexplicably terminated in the night)



The following reply was made to PR bin/57952; it has been noted by GNATS.

From: Robert Elz <kre%munnari.OZ.AU@localhost>
To: Roy Marples <roy%marples.name@localhost>
Cc: "gnats-bugs" <gnats-bugs%netbsd.org@localhost>
Subject: Re: bin/57952 (dhcpcd(8) inexplicably terminated in the night)
Date: Sat, 24 Feb 2024 05:35:05 +0700

     Date:        Fri, 23 Feb 2024 16:17:35 +0000
     From:        Roy Marples <roy%marples.name@localhost>
     Message-ID:  <18dd6c202ed.f0b7cc331864567.4485765256044008191%marples.name@localhost>
 
   | Would it be a good idea to adjust mtree to create the default
   | defcorename directory in the dhcpcd chroot directory with
   | appropriate permissions?
 
 The "default defcorename directory" (if I understand what you were
 asking about) is "." - which I assume already exists with what someone
 believes are appropriate permissions.
 
 The suggestion was to temporarily (globally, there's no local setting
 available for this) alter that to be "/tmp" while looking for this issue
 which would result in all core dumps being placed in /tmp - and of
 course, when in a chroot, the /tmp being used is one inside the chroot.
 
 Creating that (as a standard thing) would seem to be not the right thing
 to do - unless having a writeable (to the dhcpcd process owner) /tmp
 directory in the chroot would be useful for some other purpose.
 
 There is of course no real reason for /tmp to be the name chosen,
 except that it exists in the (non-chroot) normal environment, and is
 (almost always) writeable by anyone, which makes it work OK for this.
 But one could avoid cluttering it (given it is usually a tmpfs) with
 potentially large core files (like when firefox decides to abort) and
 instead make a similar kind of directory in a larger filesystem, and
 use that (and make the corresponding thing in the chroot).   As that
 other thing might be anywhere, depending upon available space, attempting
 to standardise it seems difficult.
 
 kre
 


Home | Main Index | Thread Index | Old Index