Date: Sun, 21 Apr 2024 12:30:49 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 278507] net/gmid: starts too early during boot, before its root documents folder has been mounted (before mountlate) Message-ID: <bug-278507-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D278507 Bug ID: 278507 Summary: net/gmid: starts too early during boot, before its root documents folder has been mounted (before mountlate) Product: Ports & Packages Version: Latest Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: freebsd@juicer.orange-carb.org CC: freebsd@omarpolo.com Flags: maintainer-feedback?(freebsd@omarpolo.com) CC: freebsd@omarpolo.com Created attachment 250134 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D250134&action= =3Dedit Patch to add LOGIN to rcorder require line in rc.d/gmid /usr/local/etc/rc.d/gmid is running too early--before the system has fully mounted all of its filesystems, in particular those with the 'late' flag in /etc/fstab. Users wishing to chroot the gmid daemon as recommended, but who are on zfs,= may establish a nullfs mount for gmid that has the 'late' flag set. For example= , to mount a read-only copy of the gmid document root within the chroot area at boot. If rc.d/gmid is run before this mount is established gmid will not fi= nd its document root and will not launch. The attached patch file resolves this issue by adding LOGIN to the require = line in the rc.d/gmid script. As /sbin/rcorder ensures that rc.d/mountlate is run before LOGIN, all filesystem mounts will be ready for use before launching gmid. This is the same approach taken, for example, by www/apache24 and databases/mysql80-server. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-278507-7788>