10-08-2015
The action related to the TMOUT environment variable can vary from shell to shell. It is completely ignored by some shells, and behaves as you specified in some shells (e.g., bash and ksh). In some implementations of ksh (and maybe other shells), a default maximum value can be built into the shell that cannot be overridden by setting TMOUT to 0.
I have no idea whether or not shells on AIX have TMOUT limits built into them, nor, if there are, whether they vary from release to release. And you haven't told us what shell is being used.
8 More Discussions You Might Find Interesting
1. Solaris
I am running solaris 8 on an ultra 10...
Every so often it has an issue with the time...
The time seems to stop - ie. when I issue the date command the time is not changing... therefore anything in cron doesnt run.
When I set the date again - its fine for a few weeks and then it pauses again.... (3 Replies)
Discussion started by: frustrated1
3 Replies
2. HP-UX
I am trying to periodically check that the environment variables have not been changed on a HP-UX server. This was going to be easy except I ran into the odd circumstance of having two files that should be created equally be created differently when one is created by command line and the other is... (1 Reply)
Discussion started by: Emancipator
1 Replies
3. Shell Programming and Scripting
Hi guys,
I know that this topic has been discuss numerous times, and I have search the net and this forum for it.
However, non able to address the problem I faced so far.
I am on Solaris Platform and unable to install additional packages like the GNU date and gawk to make use of their... (5 Replies)
Discussion started by: DrivesMeCrazy
5 Replies
4. Shell Programming and Scripting
Hi Guys,
Could you tell me how you can get the time stamp for 60th minutes?
Currently, we name our file using time stamp upto minutes and then add seconds at the end starting from 01.
And when the seconds reaches 60 we simply add 1 to the time stamp and reset the seconds to 00.
But the... (3 Replies)
Discussion started by: supaLucas
3 Replies
5. Red Hat
Hi,
My Linux VMs are running on citrix XEN.Somehow the time drift is too high (going very fast). Even if the correct time configured using date -s command, for every 1 hr it is differing almost 5 - 10 mins.
Tried configuring ntpd (local NTP server) and still it is not synchronized.
Machine... (2 Replies)
Discussion started by: uday123
2 Replies
6. Linux
This is more of an annoyance than an actual production issue. I've set it up so that each user's home directory is mounted to an immediate subdirectory of $HOME when they login, (and umounts when they log out to keep /proc/mounts a manageable size).
My issue comes in when my login scripts... (0 Replies)
Discussion started by: thmnetwork
0 Replies
7. Red Hat
Hi, I am facing a weird file access time issue on redHat5.x. I have a program which will scan the files in the NFS system and delete files which are older than 4 days, before deleting files program will print the access time of the file.
Some of the files are getting deleted which are not older... (1 Reply)
Discussion started by: Satyak
1 Replies
8. UNIX for Advanced & Expert Users
Hi All
Appreciate your help.
Here is the scenario:
1. Five months back we configured md5 authentication with network devices and NTP server and it worked fine.
2.Last week all of a sudden the network devices are out of sync.
3.We changed the md5 key and it started working.
... (0 Replies)
Discussion started by: iqtan
0 Replies
LEARN ABOUT CENTOS
vfs_readonly
VFS_READONLY(8) System Administration tools VFS_READONLY(8)
NAME
vfs_readonly - make a Samba share read only for a specified time period
SYNOPSIS
vfs objects = readonly
DESCRIPTION
This VFS module is part of the samba(7) suite.
The vfs_readonly VFS module marks a share as read only for all clients connecting within the configured time period. Clients connecting
during this time will be denied write access to all files in the share, irrespective of their actual access privileges.
This module is stackable.
OPTIONS
readonly:period = BEGIN, END
Only mark the share as read only if the client connection was made between the times marked by the BEGIN and END date specifiers. The
syntax of these date specifiers is the same as that accepted by the -d option of GNU date(1).
EXAMPLES
Mark all shares read only:
[global]
vfs objects = readonly
Mark the [backup] share as read only during business hours:
[backup]
path = /readonly
vfs objects = readonly
readonly:period = readonly:period = "today 9:00","today 17:00"
VERSION
This man page is correct for version 3.0.25 of the Samba suite.
AUTHOR
The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open
Source project similar to the way the Linux kernel is developed.
Samba 4.0 06/17/2014 VFS_READONLY(8)