Just got a solaris 8 blade 150 box with no users, only a root account. no one seems to know the password. I'd like to add one user. So I booted into single user mode via cdrom and added one. Can't seem to login using the new account, though. Here's what I'm using:
# useradd -d /tmp/"user" -m... (1 Reply)
Hi. I'm trying to output the current date to a cronjob log file. Nothing seems to work, echo $(date), echo `date` or just date in the script. I'm using /sbin/sh
Any ideas? Thanks, John (2 Replies)
In SCO Unix, where does useradd or adding a user through scoadmin (gui) pick the initial default .profile (login profile) that is put in the users home folder? In Solaris its in the /etc/skel/.profile.
I would like to replace it with a custom .profile; so that it's picked automatically when... (1 Reply)
I just installed Solaris 10 yesterday and I need to create a new username and password. I'm new to the system and I have yet to learn my way around. I appreciate all help and thank you in advance. (5 Replies)
Hello All,
New to Solaris, I added a new user by cmd " useradd -d /export/home/username -m username " but wondered when I tried to login with this new username, It doesn't automatically redirect to the user's home folder. Can anyone suggest about this? (9 Replies)
Hi,
We use a ticket system for our IT queries called OTRS. Emails sent to
that system are placed in ticket queues. OTRS reads X- headers in emails
as described here:
http://dev.jasonpruim.com/otrs/doc/X-OTRS-Headers.txt
We would like to be able to configure cron-apt to place certain X-... (1 Reply)
Hello All,
Anybody please help me to know ,what happens when a user having entry in both cron.allow and cron.deny files.Wheather the user will be able to access the crontab???
Thanks in advance
Vaisakh (5 Replies)
Hi there, I have over 2000 systems (mainly Solaris) and I want to write a script that inserts a new root cronjob on each of those servers. obviously just adding a line to /var/spool/cron/crontabs/root looks like the easiest way, but i really dont want to have to send a HUP to crond on all boxes
... (3 Replies)
Hi
I want to execute a cron job everyday at 14:50 hrs. I have a script like this:
TMP_FILE="/tmp/tmpcron.txt"
RES=0
/usr/bin/crontab -l >> $TMP_FILE
ADD_JOB="50 14 * * * /opt/mypath/scriptname.sh"
grep "scriptname.sh" $TMP_FILE >> /dev/null
JOB_NOT_EXIST=$?
if test $JOB_NOT_EXIST... (2 Replies)
Discussion started by: saurabhkoar
2 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