10 More Discussions You Might Find Interesting
1. Solaris
I have a problem where I installed several OSes as partitions on one disk. And suddenly I cannot see Solaris 11.3 in the bios boot screen anymore. I have no clue why. Do anyone have a suggestion so I can dig further somewhere?
I first installed Solaris 11.3. Then Windows10 (gaming). Then Linux... (3 Replies)
Discussion started by: kebabbert
3 Replies
2. Solaris
System: SPARC S7-2 Server; 2x8-core CPUs; 128Gb RAM; 2x600Gb HDD.
I have been experimenting on the above system, using ldmp2v to create "clones" of my physical systems as LDoms on the server when there was an unscheduled power outage. After the system came back up I had lost my LDoms, although... (7 Replies)
Discussion started by: apmcd47
7 Replies
3. Post Here to Contact Site Administrators and Moderators
Dear admins,
it seems that some threads or even users have recently (~ 2 days or so) disappeared. Examples: giuliangiuseppe and greycells. The latter asked me for the solution I provided earlier this week.
What happened? Can you help?
Regards
Rüdiger (10 Replies)
Discussion started by: RudiC
10 Replies
4. Solaris
Can't find the data in either pool.
bash-3.00# zoneadm -z PPSMzone1 move /zpool/ppsmzone1
cannot create ZFS dataset zpool/ppsmzone1: dataset already exists
Moving across file-systems; copying zonepath /rpool/PPSMzone1...
Cleaning up zonepath /rpool/PPSMzone1...
bash-3.00# zonecfg -z... (1 Reply)
Discussion started by: LittleLebowski
1 Replies
5. AIX
Hello,
I have a scsi pci x raid controller card on which I had created a disk array of 3 disks
when I type lspv ; I used to see 3 physical disks ( two local disks and one raid 5 disk )
suddenly the raid 5 disk array disappeared ; so the hardware engineer thought the problem was with SCSI... (0 Replies)
Discussion started by: filosophizer
0 Replies
6. Solaris
Hi, I've got an issue here: After I logon to the xscf prompt of this Sun M5000 and did 'XSCF> version -c xcp', the xscf prompt disappeared. I can't get it back and can't log out.
exit
rebootxscf
logout
#.
#>
#>
~#
~#
exit
sendbreak
exit
I tried to set the Mode Switch to the service... (3 Replies)
Discussion started by: aixlover
3 Replies
7. Solaris
Hello all I was configuring a SUN 2540 raid and after a reboot the hba`s is gone.
There is no longer an entry in etc/path_to_inst for them (2 cards).
I tried a reconfigure boot several times but it does not work.
The hba`s is a SUN qlogic 2200 in x4240 server (AMD).
Using solaris 10 update7.... (6 Replies)
Discussion started by: vettec3
6 Replies
8. UNIX Desktop Questions & Answers
I'm doing an assignment for a Unix course at school.
I attempted to rename one of the shell programming questions from home to Q1 by typing:
mv home Q1
It returned a message saying
mv: cannot access home
And now there's no home or Q1 in the directory. Please help! (8 Replies)
Discussion started by: slogged
8 Replies
9. Solaris
Hi all
I have a really strange situation. This morning I ran lpstat -p and it didn't return any results. I ran lpstat -t and the scheduler is running.
How strange, it seems all the printers have disappeared from my server.
Can anyone perhaps explain to me how this is possible? (4 Replies)
Discussion started by: soliberus
4 Replies
10. UNIX for Dummies Questions & Answers
I just inst freeBSD boot installation and it didnt work for(probably my lack of knowledge) reasons but i now have to partitions in freeBSD and i really need them back for windows at the moment. i just cant find them. The bad thing is that i only got this bundled version of windows so i cant really... (2 Replies)
Discussion started by: riwa
2 Replies
CRONTAB(1) General Commands Manual CRONTAB(1)
NAME
crontab - maintain crontab files for individual users (Vixie Cron)
SYNOPSIS
crontab [ -u user ] file
crontab [ -u user ] [ -i ] { -e | -l | -r }
DESCRIPTION
crontab 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/spool/cron/crontabs, they are not intended to be edited directly.
If the /etc/cron.allow file exists, then you must be listed (one user per line) therein in order to be allowed to use this command. If the
/etc/cron.allow file does not exist but the /etc/cron.deny file does exist, then you must not be listed in the /etc/cron.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.
If both files exist then /etc/cron.allow takes precedence. Which means that /etc/cron.deny is not considered and your user must be listed
in /etc/cron.allow in order to be able to use the crontab.
Regardless of the existance of any of these files, the root administrative user is always allowed to setup a crontab. For standard Debian
systems, all users may use this command.
If the -u option is given, it specifies the name of the user whose crontab is to be used (when listing) or modified (when editing). If this
option is not given, crontab examines "your" crontab, i.e., the crontab of the person executing the command. Note that su(8) can confuse
crontab and that if you are running inside of su(8) you should always use the -u option for safety's sake.
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 -l option causes the current crontab to be displayed on standard output. See the note under DEBIAN SPECIFIC below.
The -r option causes the current crontab to be removed.
The -e option is used to edit the current crontab using the editor specified by the VISUAL or EDITOR environment variables. After you exit
from the editor, the modified crontab will be installed automatically. If neither of the environment variables is defined, then the default
editor /usr/bin/editor is used.
The -i option modifies the -r option to prompt the user for a 'y/Y' response before actually removing the crontab.
DEBIAN SPECIFIC
The "out-of-the-box" behaviour for crontab -l is to display the three line "DO NOT EDIT THIS FILE" header that is placed at the beginning
of the crontab when it is installed. The problem is that it makes the sequence
crontab -l | crontab -
non-idempotent -- you keep adding copies of the header. This causes pain to scripts that use sed to edit a crontab. Therefore, the default
behaviour of the -l option has been changed to not output such header. You may obtain the original behaviour by setting the environment
variable CRONTAB_NOHEADER to 'N', which will cause the crontab -l command to emit the extraneous header.
SEE ALSO
crontab(5), cron(8)
FILES
/etc/cron.allow
/etc/cron.deny
/var/spool/cron/crontabs
There is one file for each user's crontab under the /var/spool/cron/crontabs directory. Users are not allowed to edit the files under that
directory directly to ensure that only users allowed by the system to run periodic tasks can add them, and only syntactically correct
crontabs will be written there. This is enforced by having the directory writable only by the crontab group and configuring crontab com-
mand with the setgid bid set for that specific group.
STANDARDS
The crontab command conforms to IEEE Std1003.2-1992 (``POSIX''). This new command syntax differs from previous versions of Vixie Cron, as
well as from the classic SVR3 syntax.
DIAGNOSTICS
A fairly informative usage message appears if you run it with a bad command line.
cron requires that each entry in a crontab end in a newline character. If the last entry in a crontab is missing the newline, cron will
consider the crontab (at least partially) broken and refuse to install it.
AUTHOR
Paul Vixie <paul@vix.com> is the author of cron and original creator of this manual page. This page has also been modified for Debian by
Steve Greenland, Javier Fernandez-Sanguino and Christian Kastner.
4th Berkeley Distribution 19 April 2010 CRONTAB(1)