02-12-2013
Yes you can, this is routinely done.
10 More Discussions You Might Find Interesting
1. IP Networking
I have RedHat 9.0 installed on three of my servers (PIII - 233MHz) and want that they share a common IP address so that any request made reaches each of the servers.
Can anyone suggest how should I setup my LAN. I'm new to networking in Linux so please elaborate and would be thankful for a timely... (2 Replies)
Discussion started by: Rakesh Ranjan
2 Replies
2. Filesystems, Disks and Memory
I've got a bunch of application CDs that I use here at home under Wine. They are Windows applications and as such, some of them want to see the volume label in order for the application to run. So... just copying the CD-ROM contents to a directory doesn't work. With that in mind, what I've done... (1 Reply)
Discussion started by: deckard
1 Replies
3. Linux
Hi,
I have created symlink under /.
It is /latest Pointing to /home/users/neel_prog_V1.0.
(Note: I have created this symlink so that when version get changed I will need to change only symlink instead of doing changes in /etc/exports.)
I have shared this symlink with NFS. in /etc/exports I... (0 Replies)
Discussion started by: neel.gurjar
0 Replies
4. Web Development
I'm exploring the possibility of load balancing 2 web servers and have both access an NFS share on an NFS server. I'm wondering which types of data would need to reside on the webservers and the NFS server. Would the entire web directory (HTML, CSS, images, documents) all reside in the NFS server... (1 Reply)
Discussion started by: gaspol
1 Replies
5. High Performance Computing
I'm planning to load balance 2 web servers. I'm considering mounting an NFS share between the 2 servers so they can share the data. My question is: does this setup offset some of the benefits of load balancing? although there are 2 web servers, they both still access a single NFS server. Wouldn't... (2 Replies)
Discussion started by: gaspol
2 Replies
6. Solaris
Hi
I have a problem with NFS sharing on solaris 10, the problem simply with write permission, after do the following command, the folder still not writable from machine 2 :
on machine 1 (10.10.10.32) :
share -F nfs -o rw /u01/portalrepository/
on machine 2 (10.10.10.31) :
mount -F nfs... (35 Replies)
Discussion started by: Al-Mothafar
35 Replies
7. Solaris
Hi,
Not sure where to post this, I'm sorry and need suggestion if this is wrong section.
we are running NFS Server on Solaris 10 and client box is HP-UX 11.11 (Can't apply latest patches/upgrades as in-house appln. doesn't allow)
I am able to mount NFS shares from this Solaris box onto all... (4 Replies)
Discussion started by: prvnrk
4 Replies
8. Red Hat
Hello,
I was having few issues on my linux box, I am getting this error whenever I tried to mount a share on a client linux host.
# mount -t nfs 10.10.4.150:/data/pops_sva /mnt
mount: mount to NFS server '10.10.4.150' failed: RPC Error: Program not registered.
#
I see the error and I... (4 Replies)
Discussion started by: bobby320
4 Replies
9. UNIX for Dummies Questions & Answers
Hello,
I would like to share a 9p (Plan 9) passthrough/share to a VM via NFS (using a guest as an NFS server to share a directory from the host)
At the moment I am getting the error message: 'exportfs: /share does not support NFS export'... (2 Replies)
Discussion started by: Scratch
2 Replies
10. UNIX for Beginners Questions & Answers
We are using Solaris 11 Logical Domains. We NFS share a disk backup area from one LDom to other servers. The share is on a single 1.5 Tb LUN presented to the Control Domain, and as a virtual disk on the NFS server LDom. A 1.5 Tb zpool has been created on the LDom. We now need to provide more disk... (2 Replies)
Discussion started by: SallyB
2 Replies
cron(1M) System Administration Commands cron(1M)
NAME
cron - clock daemon
SYNOPSIS
/usr/sbin/cron
DESCRIPTION
cron starts a process that executes commands at specified dates and times.
You can specify regularly scheduled commands to cron according to instructions found in crontab files in the directory
/var/spool/cron/crontabs. Users can submit their own crontab file using the crontab(1) command. Commands which are to be executed only once
can be submitted using the at(1) command.
cron only examines crontab or at command files during its own process initialization phase and when the crontab or at command is run. This
reduces the overhead of checking for new or changed files at regularly scheduled intervals.
As cron never exits, it should be executed only once. This is done routinely by way of the svc:/system/cron:default service. The file
/etc/cron.d/FIFO file is used as a lock file to prevent the execution of more than one instance of cron.
cron captures the output of the job's stdout and stderr streams, and, if it is not empty, mails the output to the user. If the job does not
produce output, no mail is sent to the user. An exception is if the job is an at(1) job and the -m option was specified when the job was
submitted.
cron and at jobs are not executed if your account is locked. Jobs and processses execute. The shadow(4) file defines which accounts are not
locked and will have their jobs and processes executed.
Setting cron Jobs Across Timezones
The timezone of the cron daemon sets the system-wide timezone for cron entries. This, in turn, is by set by default system-wide using
/etc/default/init.
If some form of daylight savings or summer/winter time is in effect, then jobs scheduled during the switchover period could be executed
once, twice, or not at all.
Setting cron Defaults
To keep a log of all actions taken by cron, you must specify CRONLOG=YES in the /etc/default/cron file. If you specify CRONLOG=NO, no log-
ging is done. Keeping the log is a user configurable option since cron usually creates huge log files.
You can specify the PATH for user cron jobs by using PATH= in /etc/default/cron. You can set the PATH for root cron jobs using SUPATH= in
/etc/default/cron. Carefully consider the security implications of setting PATH and SUPATH.
Example /etc/default/cron file:
CRONLOG=YES
PATH=/usr/bin:/usr/ucb:
This example enables logging and sets the default PATH used by non-root jobs to /usr/bin:/usr/ucb:. Root jobs continue to use
/usr/sbin:/usr/bin.
The cron log file is periodically rotated by logadm(1M).
FILES
/etc/cron.d Main cron directory
/etc/cron.d/FIFO Lock file
/etc/default/cron cron default settings file
/var/cron/log cron history information
/var/spool/cron Spool area
/etc/cron.d/queuedefs Queue description file for at, batch, and cron
/etc/logadm.conf Configuration file for logadm
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO
svcs(1), at(1), crontab(1), sh(1), logadm(1M), svcadm(1M), queuedefs(4), shadow(4), attributes(5), smf(5)
NOTES
The cron service is managed by the service management facility, smf(5), under the service identifier:
svc:/system/cron:default
Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser-
vice's status can be queried using the svcs(1) command.
DIAGNOSTICS
A history of all actions taken by cron is stored in /var/cron/log and possibly in /var/cron/olog.
SunOS 5.10 5 Aug 2004 cron(1M)