Sponsored Content
Full Discussion: Sink or Swim
Top Forums UNIX for Dummies Questions & Answers Sink or Swim Post 311 by divern2deep on Tuesday 21st of November 2000 05:46:53 PM
Old 11-21-2000
Bug Thanks

I appreciate your advice it has helped me tremendously. I look forward to the future.

1. Can you recommend a dictionary like book on UNIX commands?

2. Perhaps another book on the overall layout (big picture) of how application software like C++, PERL, and JAVA relate to both object orientated database languages like ORACLE and SQL, and to operating system languages like UNIX and Windows NT.

3. Do all e-commerce setups fall into a similiar hardware/software design setups like CORBA? For that matter how many different design setups exist using UNIX?

I have a lot of questions, but I know you guys are busy helping each and every one of us newbies so I will just wait my turn to ask more. Thanks for all the help!!!
 

We Also Found This Discussion For You

1. Solaris

SunFire V240 CPU Heat Sink Replacement

I got a replacement Heatsink and Fan unit, but the OEM unit has the SUN Thermal Interface Material (TIM) already on the heatsink matting surface. Because mine is used it does not have the TIM. Also there are 2 different TIM material SUN used based on the Processor (1-1.28GHz uses a glue backed... (1 Reply)
Discussion started by: danneskjold0809
1 Replies
proto(4)						     Kernel Interfaces Manual							  proto(4)

NAME
proto - prototype job file for at SYNOPSIS
DESCRIPTION
When a job is submitted to or the job is constructed as a POSIX shell script (see at(1)). The job file is created in as follows: o creates a header describing the job as an job or a job. jobs submitted to all queues other than queue are listed as jobs. The header is: for an job, or for a job. o A set of POSIX shell commands is added to make the environment (see environ(5)) for the job the same as the current environment. o then copies text from the prototype file to the job file, except for special variables that are replaced by other text: Replaced by the current working directory. Replaced by the current file size limit (see ulimit(2)). Replaced by the current umask (see umask(2)). Replaced by the time at which the job should be run, expressed as seconds since January 1, 1970, 00:00 Coordinated Universal Time, preceded by a colon. Replaced by text read by from the standard input (that is, the commands provided to to be run in the job). o When a job is submitted to queue queue, uses the file as the prototype file if it exists. Otherwise, it uses the file EXAMPLES
The following file creates commands to change the current directory, file size limit, and umask in the job to their respective values as they existed when was originally run. These commands are inserted before the commands in the job: SEE ALSO
at(1), queuedefs(4). STANDARDS CONFORMANCE
proto(4)
All times are GMT -4. The time now is 04:15 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy