Sponsored Content
Top Forums UNIX for Advanced & Expert Users What do you call the > thingy in context of the shell? Post 302281166 by homeyjoe on Wednesday 28th of January 2009 09:52:27 AM
Old 01-28-2009
I've always called the > symbol a 'goesinter' but not sure if that's a old-timer saying or just something I picked up along the path of life.
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Call Telnet From Within A Shell?

Hi there, I got a big problem. For one of our customers I did a website (php) that connects to another machine "A" (server) to machine "B" via expect. Now he wants that after the the connection with "B" is established, a telnet connection to "C" is opened, and some commands are executed.... (2 Replies)
Discussion started by: Tubbietoeter
2 Replies

2. Linux

a good XP file veiwing thingy for Fedora

does anyone know where i can find somthing that will let me read my XP folder withing Fedora Core? :D (5 Replies)
Discussion started by: xcaliber
5 Replies

3. Shell Programming and Scripting

how can i call one korn shell from a shell

Hi guys, please help me I have a ksh script (second picture down), in that script I define the function DATECALC. Now I want to use this function KSH in a program shell. How can I call this ksh from my shell program? My shell program is... in the first two lines I tried to call... (1 Reply)
Discussion started by: acevallo
1 Replies

4. Shell Programming and Scripting

Shell Script to call another function

Here is the following code : 1. # gcc -c test firstprog.c the above command will generate a executable file called "test " in which ever directory it is run. Assuming It will also return a value. 2. In the below SCRIPT . test is a file generated by compiling a c program... (3 Replies)
Discussion started by: Vabiosis
3 Replies

5. Red Hat

how to call a particular function from one shell another shell script

please help me in this script shell script :1 *********** >cat file1.sh #!/bin/bash echo "this is first file" function var() { a=10 b=11 } function var_1() { c=12 d=13 (2 Replies)
Discussion started by: ponmuthu
2 Replies

6. Shell Programming and Scripting

Shell Call

Can someone help me figure out how to call a c program from this shell script? I want to echo a #9 option and have it call and execute a c file called dmcc.c. #!/bin/sh # dmc.sh #clear # display menu   while : do echo "1. Display date and time." echo "2. Display what users are doing."... (7 Replies)
Discussion started by: jiro
7 Replies

7. Shell Programming and Scripting

How to call a function in Shell..?

#!/bin/bash FUN_ECHO(){ echo $1 } FUN_ECHO "hi how are you ?" This code will work fine. BUT is it possible to make the following to work ? FUN_ECHO "hi how are you ?" FUN_ECHO(){ echo $1 } I know that the code will be executed line by line. But i have a number of... (5 Replies)
Discussion started by: linuxadmin
5 Replies

8. Shell Programming and Scripting

Opening Child Shell & Executing a script in the same context

Hi, Is the below possible (SHELL = tcsh)? -- I want to write an 'alias' something like this - alias set_my_work "setenv SOME_VAR;tcsh -i;source work_script.cshrc" The intention is to run this alias and enter a child shell, at the same time ensuring that the work_script.cshrc is source-ed.... (0 Replies)
Discussion started by: mishra.a.c
0 Replies

9. Shell Programming and Scripting

Questions related to if in awk context and if without awk context

I wrote this code, questions follow #! /bin/bash -f # Purpose - to show how if syntax is used within an awk clear; ls -l; echo "This will print out the first two columns of the inputted file in this directory"; echo "Enter filename found in this directory"; read input; ... (11 Replies)
Discussion started by: Seth
11 Replies
WDOGCTL(8)						    BSD System Manager's Manual 						WDOGCTL(8)

NAME
wdogctl -- Watchdog timer control utility SYNOPSIS
wdogctl wdogctl -d wdogctl -e [-A] [-p seconds] timer wdogctl -k [-A] [-p seconds] timer wdogctl -t wdogctl -u [-A] [-p seconds] timer wdogctl -x [-A] [-p seconds] timer DESCRIPTION
wdogctl is used to manipulate watchdog timers. Watchdog timers provide a means of ensuring that a system continues to make progress. This is accomplished by use of a timer, provided by either hardware or software; when the timer expires, the watchdog resets the system. In this case of a hardware watchdog timer, this is accomplished by asserting the system's hardware reset signal. In the case of a software watchdog timer, this is accomplished by calling the kernel's normal reboot path. In order to prevent the system from rebooting, something must refresh the timer to prevent it from expiring. The NetBSD kernel provides three basic modes in which watchdog timers may operate: kernel tickle mode, user tickle mode, and external tickle mode. In kernel tickle mode, a timer in the kernel refreshes the watchdog timer. In user tickle mode, wdogctl runs in the background and refreshes the watchdog timer. In kernel tickle mode, progress of the kernel is ensured. In user tickle mode, the ability for user programs to run within a known period of time is ensured. Note that user tickle mode must be used with caution; on a heavily loaded system, the timer may expire accidentally, even though user programs may be making (very slow) progress. A user-mode timer is disarmed (if possible) when the device is closed, unless the timer is activated with the -x option. External-mode watchdogs are similar to user-mode watchdogs, except that the tickle must be done explicitly by a separate invocation of the program with the -t option. In the first two modes, an attempt is made to refresh the watchdog timer in one half the timer's configured period. That is, if the watchdog timer has a period of 30 seconds, a refresh attempt is made every 15 seconds. If called without arguments, wdogctl will list the timers available on the system. When arming a watchdog timer, the timer argument is the name of the timer to arm. Only one timer may be armed at a time; if an attempt is made to arm a timer when one is already armed, an error message will be displayed and no action will be taken. The options are as follows: -A When arming a timer, this flag indicates that an audible alarm is to sound when the watchdog timer expires and resets the system. If the selected timer does not support an audible alarm, this option will be silently ignored. -d This flag disarms the currently active timer. Note that not all watchdog timers can be disabled once armed. If the selected timer can not be disabled, an error message will be displayed and the timer will remain armed. -e Arm timer in external tickle mode. -k Arm timer in kernel tickle mode. -p period When arming a timer, this flag configures the timer period to period seconds. If the specified period is outside the timer's range, an error message will be displayed and no action will be taken. -t This flag tickles an external mode timer. -u Arm timer in user tickle mode. -x Arm timer in a modified user tickle mode: closing the device will not disarm the timer. FILES
/dev/watchdog -- the system monitor watchdog timer device SEE ALSO
acpiwdrt(4), evbarm/iopwdog(4), i386/elansc(4), i386/gcscpcib(4), i386/geodewdog(4), ipmi(4), itesio(4), pcweasel(4), pwdog(4), swwdog(4), x86/ichlpcib(4) HISTORY
The wdogctl command first appeared in NetBSD 1.6. AUTHORS
The wdogctl command and the NetBSD watchdog timer framework were written by Jason R. Thorpe <thorpej@zembu.com>, and contributed by Zembu Labs, Inc. BSD
August 11, 2011 BSD
All times are GMT -4. The time now is 09:32 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy