04-23-2009
Quote:
Originally Posted by
sandholm
You didn't indicate what release of Linux/Unix you were using.
Check man pages for pam_login.
some setting may come from /etc/login.defs
Sorry, It's Solaris8. I'll have a look at the man pages for that.
Cheers!
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I'm using Linux-Mandrake 8.0 in my laptop. After I logged in as a "root", I added a new path in my .bashrc file (I use bash shell). Then I can observe it has been set correctly by typing echo $PATH.
But, when I log in again as a personal account, not "root", then I open my bash shell, and type... (5 Replies)
Discussion started by: yishen
5 Replies
2. UNIX for Dummies Questions & Answers
I am a corporate user of Solaris ?? I have to write a lot of scripts to do little repetitive actions. To make this easier I would like to set the PATH so that I do not have to type ./ first before the script name.
Is there an easy script that will allow me to set this path when I log in???
... (2 Replies)
Discussion started by: jagannatha
2 Replies
3. Solaris
hi
how do i change the default PATH in my system.
i log in as root, and i have .profile file in my / directory. ive put the PATH=.:/usr.......... statement, but that doesnt seem to be working
i also wanted to know why exactly we need the profile file in etc? (6 Replies)
Discussion started by: strider
6 Replies
4. UNIX for Dummies Questions & Answers
Hey eveyone, I am new to unix, and I just installed java 6, however it doesn't recognize javac command
I tried to set the path such as:
set path="/usr/java/jdk1.6.0_06/bin/
but i still got the same error message.
any ideas?
-andi (1 Reply)
Discussion started by: adtd8
1 Replies
5. Solaris
Hi,
I want to set the path for my application so I am setting the path as below --
PATH=${PATH}:.:/envs/mldev/tools:/envs/mldev/common/tools:${HOME}:/bin/p4v:/usr/j2se:/usr/j2se/bin:/usr/j2se/lib
or
PATH="\
/usr/bin:\
/usr/sbin:\
/usr/dt/bin:\
... (7 Replies)
Discussion started by: smartgupta
7 Replies
6. Solaris
Hi all,
I am trying ping command in SUN v240 server but it is not working
but when i am using the full path
/usr/sbin/ping <ip address> then it is working.
how to set the path of ping command so that by simply typing
ping <ip address>
it should work ?
Plz help me out:( (7 Replies)
Discussion started by: saurabh84g
7 Replies
7. UNIX for Dummies Questions & Answers
Very new to this type of thing so go easy on me.......
I have downloaded a command language for data display.
It came as ncl_ncarg-5.2.1.MacOS_10.6_i386_64bit_gcc421.tar.gz and I unzipped/tarred it into my local directory.
The new directory, ncl_ncarg-5.2.1.MacOS_10.6_i386_64bit_gcc421,... (7 Replies)
Discussion started by: davcra
7 Replies
8. UNIX for Dummies Questions & Answers
Something changed on my unix box.
Now when I log in it is showing entire path. It used to show only $ prompt before.
I know I need to do something in .profile to show only $ prompt
Could you please tell me what I should do, to show only $ prompt. (4 Replies)
Discussion started by: raopatwari
4 Replies
9. UNIX for Dummies Questions & Answers
OS Platform : Oracle Linux 6.5
We are creating a shell script to purge old log files . It uses find command with rm in it.
The syntax is
find <Path of Log Directory> -exec rm -fr {} \;
Example:
find /tmp/test3 -exec rm -fr {} \;
For rm command , we use -r option to... (4 Replies)
Discussion started by: kraljic
4 Replies
10. Shell Programming and Scripting
Hi Folks -
I was wondering if you could help convert batch code in Linux? For instance, I use the following piece of code in DOS to find a file/executable, and then the FULL path as a variable.
::-- If startMaxl.exe exists, set full path --::
for %%D in (c d e f g h i j k l m n o p q r s t... (4 Replies)
Discussion started by: SIMMS7400
4 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)