06-02-2011
Assuming any user logged in gets killed, what's in root's crontab at or just before that time?
And what's in /var/adm/messages about that time?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I have a general question on using the "nohup" command. As far as I've got it, submmitting a job with no hang up specified, should result in the job running until completion, regardless of whether the session that submitted the job(parent) is still active. This is very helpful when doing... (1 Reply)
Discussion started by: errolg
1 Replies
2. UNIX for Dummies Questions & Answers
Hello
a few Q's that if anyone knows the answer to i would be grateful:
:confused: when exiting a terminal session run through a windows environment i can either type exit or use ctrl +D. I was wondering if one way was a 'cleaner' method to exit then the other or whether it is executed the... (2 Replies)
Discussion started by: hu$h
2 Replies
3. UNIX for Advanced & Expert Users
There's a user that opens various login sessions with a particular SOLARIS server at the same time - this locks the server thats tried to get logged into..
Kindly help on how to know the max limit of sessions a particular user can open with a particular server at the same time. AND, how to... (2 Replies)
Discussion started by: its.simron
2 Replies
4. Solaris
I am trying to install Solaris 10 on a target machine which is t1000. ( sun4v). I have configured my jumpstart server to install solaris over WAN. when i boot my machine, the wanboot image gets downloaded properly, miniroot gets downloaded properly, but after that the process fails with the... (3 Replies)
Discussion started by: hemalsid
3 Replies
5. UNIX Desktop Questions & Answers
I would like to use a terminal session to ssh to switches and routers. I need to capture data while logged into switches to a file I can email for troubleshooting.
I use termial to log into Cisco switch, run the sh tech command, and then sent the output to cisco. Is there a way to run a... (4 Replies)
Discussion started by: tdelliott
4 Replies
6. Solaris
I just installed Solaris 10 - 10/08 x86 and want to be able to connect remotely from either my other Sparc Sun box or Xwin32 or Cygwin-X to it. For some reason unlike my Solaris 10 Sparc install the X for remote does not seem to be running or working properly. What do I need to do to make this work... (5 Replies)
Discussion started by: lacakid
5 Replies
7. UNIX for Dummies Questions & Answers
Hi I am working in Solaris 10 and I want to monitor logs for every telnet/ssh session that tries to connect to the server. I need these logs to be generated in a file that I can fetch using ftp.
I am a new user and a stepwise detail will be great
BR
saGGee (3 Replies)
Discussion started by: saggee
3 Replies
8. Shell Programming and Scripting
Hi,
I would normally clear off the history entries from a terminal by using the following commands:
> ~/.bash_history
history -c
But this will remove the entries of that particular session only. How to prune all the entries of all login sessions for a particular user in a system?
N.B:... (3 Replies)
Discussion started by: royalibrahim
3 Replies
9. Shell Programming and Scripting
Hi All,
Can someone help me in knowing the exact difference between nohup and &.
The definition is quite clear but i only want to know if i run my job using & and in between i hung up my terminal. (10 Replies)
Discussion started by: Uinx_addic
10 Replies
10. Shell Programming and Scripting
Shell : bash
OS : Oracle Linux 6.4
I want to save the ouput of a nohup command to file other than nohup.out . Below are my 3 attempts.
For both Attempt1 and Attempt2 , the redirection logs the output correctly to the output file. But I get the error "ignoring input and redirecting stderr to... (7 Replies)
Discussion started by: kraljic
7 Replies
LEARN ABOUT FREEBSD
crontab
CRONTAB(1) BSD General Commands Manual CRONTAB(1)
NAME
crontab -- maintain crontab files for individual users (V3)
SYNOPSIS
crontab [-u user] file
crontab [-u user] { -l | -r | -e }
DESCRIPTION
The crontab utility is the program used to install, deinstall or list the tables used to drive the cron(8) daemon in Vixie Cron. Each user
can have their own crontab, and though these are files in /var, they are not intended to be edited directly.
If the allow file exists, then you must be listed therein in order to be allowed to use this command. If the allow file does not exist but
the deny file does exist, then you must not be listed in the deny file in order to use this command. If neither of these files exists, then
depending on site-dependent configuration parameters, only the super user will be allowed to use this command, or all users will be able to
use this command. The format of these files is one username per line, with no leading or trailing whitespace. Lines of other formats will
be ignored, and so can be used for comments.
The first form of this command is used to install a new crontab from some named file or standard input if the pseudo-filename '-' is given.
The following options are available:
-u Specify the name of the user whose crontab is to be tweaked. If this option is not given, crontab examines ``your'' crontab, i.e.,
the crontab of the person executing the command. Note that su(1) can confuse crontab and that if you are running inside of su(1) you
should always use the -u option for safety's sake.
-l Display the current crontab on standard output.
-r Remove the current crontab.
-e Edit the current crontab using the editor specified by the VISUAL or EDITOR environment variables. The specified editor must edit
the file in place; any editor that unlinks the file and recreates it cannot be used. After you exit from the editor, the modified
crontab will be installed automatically.
FILES
/var/cron/allow List of users allowed to use crontab
/var/cron/deny List of users prohibited from using crontab
/var/cron/tabs Directory for personal crontab files
DIAGNOSTICS
A fairly informative usage message appears if you run it with a bad command line.
SEE ALSO
crontab(5), cron(8)
STANDARDS
The crontab command conforms to IEEE Std 1003.2 (``POSIX.2'') with the exception that the dangerous variant of calling crontab without a file
name in the first form of the command is not allowed by this implementation. The pseudo-filename '-' must be specified to read from standard
input. The new command syntax differs from previous versions of Vixie Cron, as well as from the classic SVR3 syntax.
AUTHORS
Paul Vixie <paul@vix.com>
BSD
May 13, 2010 BSD