05-03-2011
There is some extravagant scripts running on all 70(ish) LPARs from that share which I think is likely somehow creating hidden unlinked files or a whack of cache as you suggest. I didn't write them so I am digging through and correcting potential culprits in hopes of stumbling upon the issue. Nothing jumps out at me but there is many lines of code to look through.
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. 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
4. AIX
Hi folks,
Just get my 1st AIX 6.1 servers up and creating some NFS shares without issues.
I can mount it from others AIX 6.1 systems but can't from 5.3. Permissions etc. are OK
lcppa1261 45: pbrun mount lcppa1001:/export/images /mnt
NFS server lcppa1001 not responding still trying... (1 Reply)
Discussion started by: unclefab
1 Replies
5. 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
6. Solaris
Hello all,
I am having an issue with an NFS share I have created between two Solaris 10 boxes. I want the share to have read/write permissions, but for some reason it is coming up as read-only on the client side mount despite "rw" being specified in the mount options.
Here is what I have... (6 Replies)
Discussion started by: fallersaur
6 Replies
7. 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
8. 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
9. Red Hat
I am having an issue with getting the proper group settings on NFS-shared directories.
NFS server, NFServe, nfs-shares hundreds of project directories...running Solaris 10 latest patches/updates.
SAS server, SAServe, statistical analysis server running on RedHat 7 with latest kernel/patches/etc.... (14 Replies)
Discussion started by: cjhilinski
14 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
LEARN ABOUT DEBIAN
syslogout
SYSLOGOUT(8) System Manager's Manual SYSLOGOUT(8)
NAME
syslogout - modular centralized shell logout mechanism
DESCRIPTION
syslogout is a generic approach to enable centralized shell logout actions for all users of a given system in a modular and centralized way
mostly aimed at avoiding work for lazy sysadmins. It has only been tested to work with the bash shell.
It basically consists of the small /etc/syslogout shell script which invokes other small shell scripts having a .bash suffix which are con-
tained in the /etc/syslogout.d/ directory. The system administrator can drop in any script he wants without any naming convention other
than that the scripts need to have a .bash suffix to enable automagic sourcing by the /etc/syslogout script.
For shell sessions, the contents of /etc/syslogout.d/" will be sourced by every user at logout if the following lines are present in his
$HOME/.bash_logout:
if [ -f /etc/syslogout ]; then
. /etc/syslogout
fi
If used for X sessions it is advisable to include the former statement into the Xreset script of the X display manager instead to prevent
that closing of an terminal emulator window yields unexpected results in your running X session if your X11 terminal emulator is using a
login shell. Be sure then to run it under the user-id of the X session's user. See the example files in /usr/share/doc/syslogout/ for
illustration.
Users not wanting /etc/syslogout to be sourced for their environment can easily disable it's automatic mechanism. It can be disabled by
simply creating an empty file called $HOME/.nosyslogout in the user's home directory using e.g. the touch(1) command.
Any single configuration file in /etc/syslogout.d/ can simply be overridden by any user by creating a private $HOME/.syslogout.d/ directory
which may contain a user's own version of any configuration file to be sourced instead of the system default. It's names have just to
match exactly the system's default /etc/syslogout.d/ configuration files. Empty versions of these files contained in the $HOME/.syslo-
gout.d/ directory automatically disable sourcing of the system wide version.
Naturally, users can add and include their own private scripts to be automagically executed by /etc/syslogout at logout time.
OPTIONS
There are no options other than those dictated by shell conventions. Anything is defined within the configuration scripts themselves.
SEE ALSO
The README files and configuration examples contained in /usr/share/doc/syslogout/ and the manual page for bash(1), xdm(1x),
xdm.options(5), and wdm(1x). Recommended further reading is everything related with shell programming.
If you need a similar mechanism for executing code at login time check out the related package sysprofile(8) which is a very close compan-
ion to syslogout.
BUGS
syslogout in its current form is mainly restricted to bash(1) syntax. In fact it is actually a rather embarrassing quick and dirty hack
than anything else - but it works. It serves the practical need to enable a centralized bash configuration until something better
becomes available. Your constructive criticism in making this into something better" is very welcome. Before i forget to mention it: we
take patches... ;-)
AUTHOR
syslogout was developed by Paul Seelig <pseelig@debian.org> specifically for the Debian GNU/Linux system. Feel free to port it to and use
it anywhere else under the conditions of either the GNU public license or the BSD license or both. Better yet, please help to make it into
something more worthwhile than it currently is.
SYSLOGOUT(8)