Date included Post: 302990480

6 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

PS1 with date stamp included in prompt

How would I put the date within my PS1 command for my shell prompt? I have it set to: PS1='$>' I tried PS1='$>' but that didn't work.

2. UNIX for Dummies Questions & Answers

Addition with the prefixing zeros included

Hi I need to do an add function but it should include the prefixed zeros For Example i=00123 j=`expr $i + 1` The output it shows is 124 but I want the output to be 00124 Could any one help me finding out how to do this Thanks

3. Solaris

What update level included fcinfo?

Hi all first post here. quick question what Solaris 10 update level included this utility? I have a bunch of Sun boxes at varying levels of Solaris 10 some have it some do not. When I do my install I take the full option for the packages to install on all the systems. thanks in advance... Mike

4. Programming

Compile error from included headers

Hello, I have an error when I include the socket.h linux header and compile with gcc. In file included from /usr/include/sys/socket.h:40:0, from test.c:17: /usr/include/bits/socket.h:217:5: error: expected identifier before numeric constant In test.c:17: #include...

5. UNIX for Dummies Questions & Answers

Create a condition for a non-included string

hey, just want to ask how to check this scenario a="apple banana cherry" if egg=0 fi how do you do the condition? thanks!

6. Shell Programming and Scripting

Rm -rf file.txt~ included in the first step?

I need to shred and delete a file after a certain time. Therefore I use shred -z /path/to/file.txt | rm -rf /path/to/file.txtIt works well, but typing in that very directory ls -shiI still see the so called backup-copy lets say file.txt~ When running bleachbit it will disappear thoroughly....

LEARN ABOUT BSD

at

AT(1)							      General Commands Manual							     AT(1)

NAME

       at - execute commands at a later time

SYNOPSIS

       at [ -c ] [ -s ] [ -m ] time [ day ] [ file ]

DESCRIPTION

       At spools away a copy of the named file to be used as input to sh(1) or csh(1).	If the -c flag (for (csh(1))) or the -s flag (for (sh(1)))
       is specified, then that shell will be used to execute the job; if no shell is specified, the current environment shell is used.	If no file
       name is specified, at prompts for commands from standard input until a ^D is typed.

       If  the -m flag is specified, mail will be sent to the user after the job has been run. If errors occur during execution of the job, then a
       copy of the error diagnostics will be sent to the user. If no errors occur, then a short message is sent informing the user that no  errors
       occurred.

       The  format  of the spool file is as follows: A four line header that includes the owner of the job, the name of the job, the shell used to
       run the job, and whether mail will be set after the job is executed. The header is followed by a cd command to the current directory and  a
       umask command to set the modes on any files created by the job.	Then at copies all relevant environment variables to the spool file.  When
       the script is run, it uses the user and group ID of the creator of the spool file.

       The time is 1 to 4 digits, with an optional following `A', `P', `N' or `M' for AM, PM, noon or midnight.  One and  two  digit  numbers  are
       taken to be hours, three and four digits to be hours and minutes.  If no letters follow the digits, a 24 hour clock time is understood.

       The  optional  day is either (1) a month name followed by a day number, or (2) a day of the week; if the word `week' follows, invocation is
       moved seven days further off.  Names of months and days may be recognizably truncated.  Examples of legitimate commands are

	      at 8am jan 24
	      at -c -m 1530 fr week
	      at -s -m 1200n week

       At programs are executed by periodic execution of the command /usr/libexec/atrun from cron(8).  The granularity of at depends upon the  how
       often atrun is executed.

       Error output is lost unless redirected or the -m flag is requested, in which case a copy of the errors is sent to the user via mail(1).

FILES

       /usr/spool/at		    spooling area
       /usr/spool/at/yy.ddd.hhhh.*  job file
       /usr/spool/at/past	    directory where jobs are executed from
       /usr/spool/at/lasttimedone   last time atrun was run
       /usr/libexec/atrun		executor (run by cron(8))

SEE ALSO

       atq(1), atrm(1), calendar(1), sleep(1), cron(8)

DIAGNOSTICS

       Complains about various syntax errors and times out of range.

BUGS

       Due  to	the  granularity  of  the execution of /usr/libexec/atrun, there may be bugs in scheduling things almost exactly 24 hours into the
       future.

       If the system crashes, mail is not sent to the user informing them that the job was not completed.

       Sometimes old spool files are not removed from the directory /usr/spool/at/past. This is usually due to a system crash, and  requires  that
       they be removed by hand.

4th Berkeley Distribution					 October 21, 1996							     AT(1)