So I have some filesystems in /mnt/whatever, /l/x, /l/y/z that are exported over nfs. FC3 used to be able to export them fine, but in yesterday's rawhide tree, mountd fails to stat the exported mount points, so everything falls apart. bug 118946 seems to imply this should be fixed, but it doesn't work for me. Should I reopen that bug, or create a new one?
Alexandre Oliva wrote:
So I have some filesystems in /mnt/whatever, /l/x, /l/y/z that are exported over nfs. FC3 used to be able to export them fine, but in yesterday's rawhide tree, mountd fails to stat the exported mount points, so everything falls apart. bug 118946 seems to imply this should be fixed, but it doesn't work for me. Should I reopen that bug, or create a new one?
Do you have the nfs booleans turned on?
nfs_export_all_ro --> inactive nfs_export_all_rw --> inactive
On Jan 27, 2005, Alexandre Oliva aoliva@redhat.com wrote:
So I have some filesystems in /mnt/whatever, /l/x, /l/y/z that are exported over nfs. FC3 used to be able to export them fine, but in yesterday's rawhide tree, mountd fails to stat the exported mount points, so everything falls apart. bug 118946 seems to imply this should be fixed, but it doesn't work for me.
Nevermind, I was missing nfs_export_all_r[ow]. Should these perhaps be enabled by default, for backward compatibility?
Alexandre Oliva wrote:
On Jan 27, 2005, Alexandre Oliva aoliva@redhat.com wrote:
So I have some filesystems in /mnt/whatever, /l/x, /l/y/z that are exported over nfs. FC3 used to be able to export them fine, but in yesterday's rawhide tree, mountd fails to stat the exported mount points, so everything falls apart. bug 118946 seems to imply this should be fixed, but it doesn't work for me.
Nevermind, I was missing nfs_export_all_r[ow]. Should these perhaps be enabled by default, for backward compatibility?
They should be turned on in a fresh install this is the booleans file currently in targeted
File Edit Options Buffers Tools Help allow_kerberos=1 allow_ypbind=1 ftpd_is_daemon=1 ftp_home_dir=1 httpd_enable_cgi=1 httpd_enable_homedirs=1 httpd_ssi_exec=1 httpd_tty_comm=0 httpd_unified=1 named_write_master_zones=0 read_default_t=1 nfs_export_all_ro=1 nfs_export_all_rw=1 stunnel_is_daemon=0 use_nfs_home_dirs=0
They are turned off by default on strict.
On Jan 27, 2005, Daniel J Walsh dwalsh@redhat.com wrote:
Alexandre Oliva wrote:
Nevermind, I was missing nfs_export_all_r[ow]. Should these perhaps be enabled by default, for backward compatibility?
They should be turned on in a fresh install
I had an all-new rawhide install on Wednesday or so (not sure whether I did the install on Wednesday with the previous day's rawhide, or used Wednesday's rawhide for an install on Thursday), and they certainly were not active. Maybe the bug was fixed since then?
On Jan 29, 2005, Alexandre Oliva aoliva@redhat.com wrote:
I had an all-new rawhide install on Wednesday or so (not sure whether I did the install on Wednesday with the previous day's rawhide, or used Wednesday's rawhide for an install on Thursday), and they certainly were not active. Maybe the bug was fixed since then?
And to make matters worse, after up2dating the box to yesterday's rawhide, the nfs_* setting was back to inactive (and 0 in the booleans config file), although I had enabled it with setsebool -P before. What gives?
Alexandre Oliva wrote:
On Jan 29, 2005, Alexandre Oliva aoliva@redhat.com wrote:
I had an all-new rawhide install on Wednesday or so (not sure whether I did the install on Wednesday with the previous day's rawhide, or used Wednesday's rawhide for an install on Thursday), and they certainly were not active. Maybe the bug was fixed since then?
And to make matters worse, after up2dating the box to yesterday's rawhide, the nfs_* setting was back to inactive (and 0 in the booleans config file), although I had enabled it with setsebool -P before. What gives?
That is strange since booleans is a %config(noreplace)
selinux@lists.fedoraproject.org