10-28-2003
Look at the man page for crontab -
Users: Access to crontab is denied:
o if /etc/cron.d/cron.allow exists and the user's name
is not in it.
o if /etc/cron.d/cron.allow does not exist and user's
name is in /etc/cron.d/cron.deny.
o if neither file exists, only a user with the
solaris.jobs.user authorization is allowed to submit a
job.
Note that the rules for allow and deny apply to root only if
the allow/deny files exist.
The allow/deny files consist of one user name per line.
10 More Discussions You Might Find Interesting
1. AIX
Trying to setup user to have the ability to delete any files (regardless of owner) in /tmp.
I've tried almost everything... the permission on the folder is drwxrwxrwt 10 bin bin, and at one point I give all the possible permission (short of root) I can give to the user, and he still can't delete... (2 Replies)
Discussion started by: cchiang12
2 Replies
2. UNIX for Dummies Questions & Answers
Hi there,
I want to change from this permission -r-xr-xr-x to -r-xr-xr-- for a set of files under unix.
Can someone help me to go-about doing this in one shot.
Cheers,
RN (2 Replies)
Discussion started by: karthickrn
2 Replies
3. Shell Programming and Scripting
Hi, all!
Is it possible to use umask and to set the file permission level as 775?
I know I can add chmod into my scripts but I just want to explore the umask option.
Thanks! (1 Reply)
Discussion started by: visio2000
1 Replies
4. Shell Programming and Scripting
Here is the sample code I'm trying to execute. I see that the permission on the file is set to 755 always I want to change it to 777. Please help me with this.
code :
#!/usr/bin/perl
use File::Path qw(make_path remove_tree);
my $path = "2010/sam";
make_path($path,{mode=>0777});
... (1 Reply)
Discussion started by: hansini
1 Replies
5. UNIX for Advanced & Expert Users
Default file system currently is 664.
I would like to get it as 774.
As other users of the same group was not able execute the file created any any user.
chmod cannot be used in my case. (Files are created and executed the programs owned by different vendors)
we know that umask is not going... (3 Replies)
Discussion started by: deepakwins
3 Replies
6. Shell Programming and Scripting
hi,
i am new in unix.......i am using bash and i want to create a user which has only some command and scripts permission.........is it possible?
thanx (1 Reply)
Discussion started by: rakeshtomar82
1 Replies
7. UNIX for Dummies Questions & Answers
Hey Guys,
First post here. I just started learning UNIX a few weeks ago.
My issue: I use FreeNAS which is based off of UNIX in my network environment which hosts files that my team needs to access. Each user has their own login but we are all part of a group called "ITLIC".
I have a share... (15 Replies)
Discussion started by: uglycustoomer
15 Replies
8. Shell Programming and Scripting
Hi Techies
I am stuck in a problem, I have written a script which is calling a second script which contains some command and password for quering on database. I do not want to disclose this command or specially password file. Please help..
Please have a look on directory structure and... (2 Replies)
Discussion started by: atul9806
2 Replies
9. UNIX for Dummies Questions & Answers
When am saving a file using my username in Linux environment, the file permission granted is rw-r--r--
I have to manually change the permissions using chmod command.
How do i write it to the disk as rw-rw-r while saving my file. (6 Replies)
Discussion started by: Avishek_rc1
6 Replies
10. UNIX for Dummies Questions & Answers
After I edit the cron job by using crontab -e and using :wq! to save, i got following error message:
"/tmp/crontabxvaarX" 1 line, 60 characters
crontab: /tmp/crontabxvaarX: Permission denied
Could anyone please help? (1 Reply)
Discussion started by: Alex Li
1 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