The programs that are running from cron don't have a tty associated with the process so there is no "screen" for your script to pop up a message in.
If you don't tell a script where to send output (the > /dev/null in typical lines), output is generally e-mailed to the account that owns the crontab. If you don't add the last bit (2>&1) to the command, anything sent to STDERR will be e-mailed.
Generally, as an admin, I'm either redirecting my crontab output to a log file (for errors) or to a specific output file. For example:
This will create a webpage that webscan generates and e-mail any errors (STDERR output) to me.
So you really can't have a popup window created from a crontab.
Just write the info to a log file and e-mail it to yourself or to a group if more than one needs to see it.
Oh, and what's the "say" command? The only reference I can find to it is the OS X say command which converts text to audio output. Just curious.
When i am trying to login to my unix machine. It is directly loging me into root ( / ) directory, instead of my home directory. Why this is happening. And generally when this happens (4 Replies)
Okee problems...!!
What is happening: Unix server with some programms, workstations are windows 2000, the workstations work good but when you start a programm on the Unix server the CPU of the workstations go to 100% usage resulting that the system gets very slow. The programm well its running so... (2 Replies)
i have a problem with installing unix
after booting system by itself floppy , during checking the hardware devices computer hangs , and stops.
it checks:
%fpu
%serial
%floppy
%console
%pci
%adapter
%tape
%cd-rom
G hd_config in this place system got stop.
remember i passed this step at... (1 Reply)
Hello,
We had a system shutdown last night and now the server won't boot because of volume is seriously damaged (this affects all volumes). Any suggestions on how to repair.
Any suggestions welcome
Thanks (1 Reply)
Hello Moto
I hope someone can help
We's here at work, have a unix box with sco openserver 5 on it, so it has a nice gui interface.. and also a fair few windows computers..
a system admin guy b4 me, has set up a user called neil, which can, when u try to access the unix box using windows... (2 Replies)
We have an older HP Unix 10.20 system that we rarely ever use anymore. Most of our jobs on it are from 1994 to 2002. Anything after that is on Windows XP. The Unix system was backed up religiously every day. Because of space constraints some of the jobs were removed from the system after a... (3 Replies)
hi,
im tring installaing sco unix 5.05 in my pc but it is showing an
"memory error loading kernel fd(64)unix.text
loading ram disk image fd(64)rootfs"
can anybody tell me how to solve this problem.
my system configuration is 3.2ghz processor,1gb ram,d101ggc mother board
thank u
bln (1 Reply)
hi all
i have written this small code.
sqlplus $schema_name/$passwrd@$instance <<eof
set serveroutput on;
declare
lv_count pls_integer;
lv_option varchar2(20);
begin
select count(*) into lv_count from all_objects where upper(object_name)=upper('$temp_file1');... (1 Reply)
Hi, how we are?
I have a problem, I have a PDF in unix and i call a Shellscript, it does :
lp -d queue archive.pdf
A simply print.
I have many printers, so in some printers the PDF is printing with a diferent margin left and right margins, it cuts the really print.
I try fix it,... (6 Replies)
Input file
I have a file with four fields.
f1,f2,f3,f4
A,1,10,00,S
B,2,20,00,00,D
C,3,100,00,00,G
I want Output like
f1|f2|f3|f4
A|1|10,00|S
B|2|20,00,00|D
C|3|100,00,00|G
please help on this (4 Replies)
Discussion started by: bharat1211
4 Replies
LEARN ABOUT NETBSD
crontab
CRONTAB(1) BSD General Commands Manual CRONTAB(1)NAME
crontab -- maintain crontab files for individual users (ISC Cron V4.1)
SYNOPSIS
crontab [-u user]
crontab [-elr]
DESCRIPTION
crontab is the program used to install, deinstall, or list the tables used to drive the cron(8) daemon in ISC Cron. Each user can have their
own crontab, and though these are files in /var/cron, they are not intended to be edited directly.
If the /var/cron/allow file exists, then you must be listed therein in order to be allowed to use this command. If the /var/cron/allow file
does not exist but the /var/cron/deny file does exist, then you must not be listed in the /var/cron/deny file in order to use this command.
If neither of these files exists, depending on the compiled in settings, only the super user will be allowed to use this command, or everyone
will be allowed to use this command. On NetBSD everyone is allowed to use this command.
The default maximum size for a crontab is 256 kilobytes, but this may be changed for all users on the system by putting the desired maximum
size (in bytes) in the /var/cron/maxtabsize file.
If the -u option is given, it specifies 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.
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.
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.
FILES
/var/cron/allow Optional list of users that are allowed to use crontab.
/var/cron/deny Optional list of users that are disallowed to use crontab.
/var/cron/maxtabsize Maximum size of crontab files. Defaults to 256 kilobytes.
/var/cron/tabs/ Directory containing the individual user crontab files, named after the user.
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''). This new command syntax differs from previous versions of Vixie Cron, as well
as from the classic Version 3 AT&T UNIX syntax.
AUTHORS
Paul Vixie <vixie@isc.org>
BSD May 6, 2010 BSD