Man command doesn't display any output amonst other problems Post: 302105325

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Man command doesn't display any output amonst other problems :-)

hi all, Newbie to Unix and AIX. So my apologies if this is in the wrong place, etc. Working on box - uname# uname -a AIX appt 3 5 00C08AAF4C00 when i type man (some valid command) it just returns me to the # prompt. Its running on the KSH shell. man was working but i was trying...

2. Solaris

Solaris 10 install doesn't display Network Connectivity prompt page

I have two Dell x86 machines on which I am attempting to install Solaris 10 from CD. I am not doing a Jumpstart install. This is my first experience in installing Solaris (or any other OS). I am following the instructions at How to Quickly Install the Solaris 10 1/06 OS The first machine...

3. UNIX for Dummies Questions & Answers

sendmail problems - no man pages

Hi all, I have a virtual dedicated unix server somewhere (not sure we can put names, so ain't putting it yet :p) anyway, I have problems using sendmail, but before I am asking for help, I don't get ANY manpages for sendmail on my machine. I would like to try and solve this on my own (the...

4. UNIX for Dummies Questions & Answers

Command display output on console and simultaneously save the command and its output

Hi folks, Please advise which command/command line shall I run; 1) to display the command and its output on console 2) simultaneous to save the command and its output on a file I tried tee command as follows; $ ps aux | grep mysql | tee /path/to/output.txt It displayed the...

5. Shell Programming and Scripting

Net::SSH::Perl->Execute any unix command & display the output in a proper form

Net::SSH::Perl ...... how to print the output in a proper format my $cmd = "ls -l"; my $ssh = Net::SSH::Perl->new($host); $ssh->login($user, $pass); my($stdout, $stderr, $exit) = $ssh->cmd("$cmd"); print $stdout; the script works fine, but i am unable to see the output...

6. Shell Programming and Scripting

background functions doesn't display their output

hello there, there's a function, in my shell script, i'd like to run in the background. here's an example: log() { local SELF=${0##*/} tty -s && echo ": $*" } some_func() { # do something log "This text is not displayed in the terminal's output when running in the...

7. Homework & Coursework Questions

man command output to a txt file

Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted! 1. The problem statement, all variables and given/known data: I am trying to outut the man command output into a text file which will help me for future reference. 2....

8. UNIX for Dummies Questions & Answers

[Solved] Custom actions in Thunar doesn't display at all.

I have came across a few websites stating some custom actions for Thunar - crunchbang ubuntu I tried inputting the stated commands to Thunar, but it doesn't display at all in mine. I tried "gksu thunar %f" ( Opens current folder with root permissions.) , but when I right click in a...

9. Shell Programming and Scripting

Need help in shell Scripting to display a output from a command

Please find my below requirement and see if you can help me on this. I am looking for a shell script which can provide me the below output. Manuall steps which i am doing now 1) First I source the File $ . ./WC_env.sh 2) Execute the command $ /app/oracle/product/mos/bin/mosotl -url...

10. SuSE

Find command doesn't pipe the output as required.

Hi, I am using below code snippet to echo/display the files found (matching a pattern from searchstring.out file) and the corresponding owner. while read j do echo "Pattern to search is:- $j" find / -name "*$j*" |\ while read k do echo "File found is:- $k" owner=$(ls...

LEARN ABOUT OSF1

queuedefs

queuedefs(4)						     Kernel Interfaces Manual						      queuedefs(4)

NAME

       queuedefs - Queue description file for at, batch, and cron commands

DESCRIPTION

       The  queuedefs  file describes the characteristics of the queues managed by cron or specifies other characteristics for cron.  Each noncom-
       ment line in this file describes either one queue or a cron characteristic.  Each uncommented line should be in one of the  following  for-
       mats.

	    q.[njobj][nicen][nwaitw] max_jobs=mjobs log=lcode

       The  fields  in these lines are as follows: The name of the queue.  Defined queues are as follows: The default queue for jobs started by at
       The default queue for jobs started by batch The default queue for jobs run from a crontab file

	      Queues d to z are also available for local use.  The maximum number of jobs that can be run simultaneously in  the  queue;  if  more
	      than  njob jobs are ready to run, only the first njob jobs will be run.  The others will be initiated as currently running jobs ter-
	      minate.  The nice(1) value to give to all jobs in the queue that are not run with a user ID of superuser.  The number of seconds	to
	      wait  before rescheduling a job that was deferred because more than njob jobs were running in that queue, or because the system-wide
	      limit of jobs executing (max_jobs) has been reached.  The maximum number of active jobs from all queues that  may  run  at  any  one
	      time.  The default is 25 jobs.  Logging level of messages sent to a log file.  The default is 4.	Defined levels are as follows:

	      level-code   level

		  0	   None

		  1	   Low

		  2	   Medium

		  3	   High

		  4	   Full

       Lines beginning with # are comments, and are ignored.

EXAMPLES

       The  following  file specifies that the b queue, for batch jobs, can have up to 50 jobs running simultaneously; that those jobs will be run
       with a nice value of 20.  If a job cannot be run because too many other jobs are running, cron will wait 60 seconds before trying again	to
       run it.	All other queues can have up to 100 jobs running simultaneously;  they will be run with a nice value of 2.  If a job cannot be run
       because too many other jobs are running cron will wait 60 seconds before trying again to run it.  b.50j20n60w

       The following file specifies that a total of 25 active jobs will be allowed by cron over all the queues at any one time, and cron will  log
       all messages to the log file.  The last two lines are comments that are ignored.  max_jobs=25 log=4 # This is a comment # And so is this

FILES

       Main cron directory The default location for the queue description file.

RELATED INFORMATION

       Commands: at(1), cron(8), crontab(1), nice(1)
       delim off

																      queuedefs(4)

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers