similar to: NIS home automount feature

Hello, Does anyone have a guide for setting up an nfs server for unattended deployment of centos5? Basically what i want to do is boot a system from CD media, pass a boot parameter nfs, and ks= options then walk away, the box goes out to the nfs server, finds the kickstart file, reads, and does it. I've got several machines and i'd rather not do manual installs. Thanks. Dave.

Hello everyone, We have a CentOS 6.3 NFSv4 server and client, and we've run into a situation where the client is unable to list "private" (chmod 700-ed) directories, even if the current user owns the directory in question. A bit more background: we're also using Samba 3.5+Winbind to provide authentication and UID/GID mapping against a Windows 2008 R2 domain controller.

Hello, we are using ctdb 4.15.5 on RHEL8 (Kernel 4.18.0-372.32.1.el8_6.x86_64) to provide NFS v3 (via tcp) to RHEL7/8 clients. Whenever an ip takeover happens most clients report something like this: [Mon Feb 13 12:21:22 2023] nfs: server x.x.253.252 not responding, still trying [Mon Feb 13 12:21:28 2023] nfs: server x.x.253.252 not responding, still trying [Mon Feb 13 12:22:31 2023] nfs: server

Samba 2.2.0 on SPARC Solaris 8 Configured with: ./configure --with-pam --with-syslog --with-quotas --with-msdfs --with-acl-support I am accessing the share \\server\mgerdts, which is itself an automounted (NFS) directory. That is, /home/mgerdts on server really exists on nfsserver. On nfsserver, rquotad is commented out of inetd.conf. Using smbclient (2.0.7, yeah I know) I do: smbclient

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-06:10.nfs Security Advisory The FreeBSD Project Topic: Remote denial of service in NFS server Category: core Module: sys_nfsserver Announced:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-06:10.nfs Security Advisory The FreeBSD Project Topic: Remote denial of service in NFS server Category: core Module: sys_nfsserver Announced:

Hi Rolan, I should have corrected that, my bad! It is an NFS client mounting the NFS server, I.e. nfsClient:/some_dir_mounted_via_nfs Si On 21/07/2015 10:20, "devzero at web.de" <devzero at web.de> wrote: >>Over ssh/nfs >>rsync -nuvaz --delete /source/ root at nfsServer.domain.co.uk: > >i don`t see nfs here, i see rsync syncing a local dir via ssh to a

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-06:10.nfs Security Advisory The FreeBSD Project Topic: Remote denial of service in NFS server Category: core Module: sys_nfsserver Announced:

Hi Uli, [Sorry for slow response, life is busy...] On Mon, 13 Feb 2023 15:06:26 +0000, Ulrich Sibiller via samba <samba at lists.samba.org> wrote: > we are using ctdb 4.15.5 on RHEL8 (Kernel > 4.18.0-372.32.1.el8_6.x86_64) to provide NFS v3 (via tcp) to RHEL7/8 > clients. Whenever an ip takeover happens most clients report > something like this: > [Mon Feb 13 12:21:22

I just upgraded to 0.22.0 from 0.18.4 and I''m running into what I think are problems due to changes in scope rules. In my site.pp manifest, I have the following: import "classes/*" node nfsserver { include nfsserver } node webserver { include webserver } class cluster1_sites { website { "example.com": ...; "example2.com": ...; } } node

Hello, I've got a little problem with NFSv4 + Kerberos. I can do a mount with Kerberos with a valid ticket, but read-only. After the mount -vvv -t nfs -o nfsv4,sec=krb5 nfsserver:/ /mount_test/ I can see: #klist: Feb 6 07:22:47 Feb 6 17:22:43 nfs/nfsserver at my.domain #/var/heimdal/kdc.log: 2013-02-06T07:28:26 TGS-REQ clientnfs at my.domain from IPv4:192.168.0.23 for nfs/nfsserver at

Hi, I noticed that my 4.8R box seems to have a NFS problem. I use a FreeBSD/i386 4.8R box as a NFS server, and a FreeBSD/i386 5-CURRENT (as of today) as the NFS client. On the client, /a (on the server) can be mounted successfully with -o rw,bg,intr,mntudp options. However, when a large amount of write operations such as "cp -r /home/ncvs /a" are performed on the client, the

Hello, I set up NFSv4 server. To make sure I set vfs.nfsd.server_min_nfsvers=4. I can check its version, for example, by tcpduming and then I can see in wireshark lines like: Network File System Program Version: 4 V4 Procedure: COMPOUND.... .... is there any easier way to check its version? I see there is nfsstat -e option which shows delegs and locks. But all other ones are combined with nfsv3

I'm needing a strategy to accomplish the following: We have AD, with Server for NIS working on the DC. I've got NIS successfully working for login - or at least the client starts to login and then complains about a lack of home dir, which is fine for now. Each AD user has a directory on a fileserver, and I'd like these to be automounted as the home directory. The share path to a

hello, My apologies for my english and for not being 100% formal in my words, I'm a system engineering student (I'll do my best effort). My name is Nicol?s Guerra, I'm from Uruguay, I work in ASSE (administration of state health services) http://www.asse.com.uy this enterprise serve the half of population of my country (1.5 million clients, thousands of employes and thousands

Hi, I’m having difficulties trying to understand the performance differences between NFS and SMB. I have used rsync (OS X) over SMB (mounted network storage) and using rsync (OS X) over SSH (NFS mounted storage) From my test, rsync over SMB builds a file list each time comparing modified source/destination, where as rsync over ssh/nfs is incredibly quicker, pretty much instant. During the

... with this error message: Preparing LDAP database... => bdb_tool_entry_put: id2entry_add failed: DB_KEYEXIST: Key/data pair already exists (-30996) => bdb_tool_entry_put: txn_aborted! DB_KEYEXIST: Key/data pair already exists (-30996) slapadd: could not add entry dn="dc=washcslab,dc=org" (line=5): txn_aborted! DB_KEYEXIST: Key/data pair already exists (-30996) Migration

intel etherexpress pro 100 nics at my lan, server with tftp, nfsserver and pxelinux running for about half a year at my lan. Hi, When I use a kernel v.2.4.20 the pxe boot loads the pxefiles, kernel and then stops asking for files from the server and complains about a "Root-NFS: No NFS server available, giving up." and messages about to insert a disk... ... the same .config used with

Hi I have a problem with displaying quotas on a NFS client running CentOS 5. It works fine in the sense that I can display the quota for a user when running the quota command as root, It does not work when running as a ordinary user as shown in the example below. What can be the cause of that? # quota exampleuser Disk quotas for user exampleuser (uid 4242): Filesystem blocks quota limit

I saw this mention in feature request #321, but here is what I have: service { "nfs" : name => $operatingsystem ? { Debian => [ "nfs-common", "nfs-kernel- server" ], Ubuntu => [ "nfs-common", "nfs-kernel- server" ],