03-02-2015
I may be running afoul of the fact that unix can have the same name for a user and a group whereas that is not permitted in Active Directory. But that doesn't explain all of the cases.
Related to the nsswitch.conf question, obviously, on the nfsserver groups is files ldap and on the RH7 machine it's files sss.
Neither system runs nscd (solaris or rh). I inherited the S10 system, so I don't know why it was set up that way. I believe there are some reported issues running NSCD in conjunction with AD on RH, but I'd have to go back and re-research that.
10 More Discussions You Might Find Interesting
1. Solaris
Hello,
I'm doing a Perl script to parse the dfstab file and find dangerous configurations (rw to everyone, root access, etc). My question is, if I have a share command like this:
share -F nfs -o ro=chrome:copper:zinc,root=chrome /usr/man
it means that the /usr/man is "rw" to everyone... (6 Replies)
Discussion started by: psimoes79
6 Replies
2. Red Hat
I got a problem while creating files on a NFS mounted share in a RHEL box. That is when I create an empty file, this is what appears on the screen
###############################################
E325: ATTENTION
Found a swap file by the name ".test.swp"
owned by: jsmith dated: Tue... (2 Replies)
Discussion started by: rcmrulzz
2 Replies
3. Linux
I´m using LDAP for groups and NFS for home dirs. My problem is as follows:
I only have a few groups, so it's not the problem everyone else had. When I've mounted a disk over NFS, I need to have my primary group in order to read in the groups I'm a member of. Secondary groups is not working.
... (0 Replies)
Discussion started by: velmont
0 Replies
4. Solaris
Hi all,
I had share the server Gemini /u10 to the server Centaurus.
/etc/dfs/dfstab
share -F nfs -o root=centaurus /u10
My problem is:
in the server Gemini the the owner for /U10 is oracle:dba
but when in the server Centaurus, I am not able to change the owner become oracle:dba, it show... (8 Replies)
Discussion started by: SmartAntz
8 Replies
5. UNIX for Advanced & Expert Users
Here is the scenario...
NFS share that is accessed every few minutes by approx 70 systems (AIX 5.3/6.1). Filesystem space is being eaten up rapidly according to df however du numbers really never change. lsof and fuser cannot see any unlinked files on either the NFS server or remote... (3 Replies)
Discussion started by: masterpengu
3 Replies
6. Solaris
Can any one tell me how to add a virtual disk from NFS share in Ldom .. i have one share /VMshare/boot.img file shared/exported from one server but i do now know how to add nfs based vdsdev as it gives primary domain cannot validate the disk. (1 Reply)
Discussion started by: fugitive
1 Replies
7. Red Hat
I am setup a samba share server which is authenticating from Active Directory.
I am able to access the share with AD user but not able to access when group defined in "valid users" parameters.
below are the steps i performed.
In smb.conf
workgroup = QASLABS
password server =... (3 Replies)
Discussion started by: sunnysthakur
3 Replies
8. Red Hat
Hi,
I have an NFS server, i want to mount that nfs share which is having around 500GB to my client system. But my client system doesnt have any free space, is it possible to mount that nfs share in my client.
Regards,
Mastan (1 Reply)
Discussion started by: mastansaheb
1 Replies
9. UNIX for Dummies Questions & Answers
Hi,
I have created a NFS share in Solaris 10 server1 and mounted it on solaris 10 server 2.But I want to change owner of the files from nobody to a particular user in client.
Which command should I use. I have tried the following but it doesn't allow to change permissions in the server2 as... (0 Replies)
Discussion started by: Rossdba
0 Replies
10. Shell Programming and Scripting
I need a help of good people with effective bash script to mount nfs shared,
By the way I did the searches, since i haven't found that someone wrote a script like this in the past, I'm sure it will serve more people.
The scenario as follow:
An NFS Client with Daily CRON , running bash script... (4 Replies)
Discussion started by: Brian.t
4 Replies
NSCD(8) BSD System Manager's Manual NSCD(8)
NAME
nscd -- name service caching daemon
SYNOPSIS
nscd [-dnst] [-i cachename] [-I cachename]
DESCRIPTION
The nscd utility is the system caching daemon. It can cache almost all types of data and is basically intended to be used with the nsswitch
subsystem. The cache is actually per-user. This means that each user can work only with the cached data that were cached by themselves, and
cannot poison the cache of other users. The nscd utility supports two types of caching:
Type Description
Common caching
Each cached element is the key+value pair. This type of caching supports policies which are applied when maximum number of cached ele-
ments is exceeded. Three policies are available: FIFO (first in - first out), LRU (least recently used) and LFU (least frequently
used). This type of caching is used with the getXXXbyname() family of functions.
Multipart caching
Each cached element is the part of the elements sequence. This type of caching is intended to be used with the getXXXent() family of
functions.
The nscd utility is able not only to cache elements, but to perform the actual nsswitch lookups by itself. To enable this feature, use the
perform-actual-lookups parameter in nscd.conf(5).
The nscd utility recognizes the following runtime options:
-n Do not daemonize; nscd will not fork or disconnect itself from the terminal.
-s Single-threaded mode. Forces using only one thread for all processing purposes (it overrides the threads parameter in the
nscd.conf(5) file).
-t Trace mode. All trace messages will be written to stdout. This mode is usually used with -n and -s flags are used for debugging
purposes.
-i cachename
Invalidates personal cache. When specified, nscd acts as the administration tool. It asks the already running nscd to invalidate
the specified part of the cache of the calling user. For example, sometimes you may want to invalidate your ``hosts'' cache. You
can specify ``all'' as the cachename to invalidate your personal cache as a whole. You cannot use this option for the cachename for
which the perform-actual-lookups option is enabled.
-I cachename
Invalidates the cache for every user. When specified, nscd acts as the administration tool. It asks the already running nscd to
invalidate the specified part of the cache for every user. You can specify ``all'' as the cachename to invalidate the whole cache.
Only the root can use this option.
FILES
/etc/nscd.conf The default configuration file.
SEE ALSO
nsdispatch(3), nscd.conf(5), nsswitch.conf(5)
AUTHORS
Michael Bushkov <bushman@FreeBSD.org>
BUGS
Please send bug reports and suggestions to <bushman@FreeBSD.org>.
BSD
October 20, 2005 BSD