Sponsored Content
Full Discussion: A little guidance needed :)
Top Forums Shell Programming and Scripting A little guidance needed :) Post 302173668 by shadow0001 on Friday 7th of March 2008 11:56:34 AM
Old 03-07-2008
I tried that however it did not work - brought up the entire line with out the option. Unix doesn't like me very much lol.

A final (i hope) question. If i had the work "command" and i wanted to split it into characters, how would i go about doing this ? See i need to be able to process each character individually using a loop however i am not aware of a command that allows me to do this.

Thanks again.
 

10 More Discussions You Might Find Interesting

1. AIX

NIM Guidance

I've just started to explore NIM and I'm looking for additional information on how to set it up and configure it. I've read through the "NIM A-Z" and have many unanswered questions. One question is how can I have the NIM server pull a mksysb of the clients and can I schedule this to happen... (1 Reply)
Discussion started by: scottsl
1 Replies

2. What is on Your Mind?

Career Guidance

Hi, I am a newbie to Unix, I was introduced to UNIX 8 months back during my Training, I was attracted to Unix as they give complete freedom. I would like to ask how can a OS Admin can go into development field of Unix. Currently I am working in a MNC in Backup- Storage Admin Domain I am... (1 Reply)
Discussion started by: sufi_431
1 Replies

3. UNIX for Advanced & Expert Users

Guidance needed for quick script

Hi all, I am trying to get the exception count daily from a log file which is more than 1 GB in size. I am using loops which get the count of the exception and transaction. But i need to take this exception count for a time frame from 5.00 am to 5:00 pm. I Think I can use to exact the... (4 Replies)
Discussion started by: senthilkumar_ak
4 Replies

4. HP-UX

HP-UX 10.20 fbackup? restore help/guidance needed

Hello, We've recently had a multiple hardrive failure in our legacy HP9000. Now the drives are repaired and the filesystems are recreated, I went to restore the last of the database tables from our dds3 backup, but cannot. Here's what's going on: BTW, I'm an absolute novice w/ HP-UX The... (5 Replies)
Discussion started by: jastuart
5 Replies

5. UNIX for Dummies Questions & Answers

Need guidance on RHEL patch

Hi, I am new with updates in RHEL especially servers. The question is: 1. Do I need to register to RHEL in order for me to use the up2date? 2. For updates in RHEL need to use up2date, but what is the thing that I need to do before the patches? I mean what should I backup in case my patches... (0 Replies)
Discussion started by: flekzout
0 Replies

6. Shell Programming and Scripting

Guidance needed for a typical shell script with sql query

Hi , I have a txt file with contents like: 1234 2345 3456 7891 I need to write a script which takes input file as txt file..run a sql query for that number and place the output of query in another file.. select * from bus_event where acct_nbr='1234'( from input txt file) the query... (20 Replies)
Discussion started by: Rajesh Putnala
20 Replies

7. AIX

Need guidance on VMStat

I need some guidance on the differences in observations, not sure how significantly different are they. Also, It would be nice to hear on the values and what the obvious tuning for performance missing. Observation 1 ending vmstat -v 3948544 memory pages ending vmstat -v ... (1 Reply)
Discussion started by: Snipper
1 Replies

8. UNIX for Dummies Questions & Answers

Just need some guidance on this nawk

Hi, I am trying to debug some KSH script and it has the nawk portion below. I just want to confirm whether I understand what it does correctly. Example usage of the nawk line is run as below: nawk '/^#/ {next} $1~/^'testp.cfg'$|^'testp.cfg'\.testdb\.com\.ph$/ { c=0 while... (1 Reply)
Discussion started by: newbie_01
1 Replies

9. Shell Programming and Scripting

Need Some guidance on scripting

Hey All, I am newbie on scripting and need some guidance from all the experts here. I am working on one project where I will check the status/health of around ten (10) solaris 10 servers. I have one central server from where I have already setup the passwordless SFTP and setup the cron... (1 Reply)
Discussion started by: supercops
1 Replies

10. AIX

New to AIX. Need Guidance

Hi There, I am new to AIX. I am eager to learn the AIX System administration or if there is any other prerequisite before this. Please can anyone help me or guide how to start with AIX, what all courses and certifications do I need to do. I have basic knowledge of UNIX. Please guide as I am... (3 Replies)
Discussion started by: rahulat302
3 Replies
win(1)							      General Commands Manual							    win(1)

NAME
win - Terminal emulator SYNOPSIS
win [-v] [-t name] [command [argument ...]] address OPTIONS
-v If the -v option is present, win prints its version number and date and exits. -tname If the -t option is present, win uses +name as the final part of the tag name of its window. DESCRIPTION
win must be able to connect to a running wily(1). win attaches to a window. If the -t option is present, the final part of the tag name is name. If command is present, the final part of the tag name is +command. Otherwise, the final part of the tag name is +win. The first part of the tag name is the current working directory. win runs a program in a child process. The child process is the leader of a process group and is connected to win by a pseudo-terminal. If command is specified, the child process runs $SHELL -c 'command argument ...' otherwise it runs $SHELL -i If SHELL is not found in the environment, /bin/sh is used. TERM=win is placed in the environment of the running program. Output from the running command appears in the window. The point after the last output from the running command is known as the output point. Further output from the running command appears just before the output point. The output point is initially at the end of the win- dow. Normal wily editing commands work in the window. When a newline, interrupt character, or end-of-file character is created after the output point, the text between the output point and the last newline, interrupt character, or end-of-file character in the window (inclusive) is passed to the running program as input. The interrupt character is control-C and the end-of-file character is control-D. The pseudo-terminal initially is configured so that these are recognized with their normal meanings. The B2 commands beginning with the |, <, or > characters or an upper case letter are executed normally by wily. Other B2 are first termi- nated with a newline, if they are not already, and are then appended to the buffer (and thereafter passed to the running program). RETURNS
win returns zero if it is able to successfully create the child process, otherwise it returns non-zero. EXAMPLES
Run a terminal emulator within wily win Run FTP within wily win ftp Run rlogin within wily win -t host.domain rlogin -8 host.domain SEE ALSO
wily(1) Tag(1) Man(1) BUGS
win doesn't follow changes to the terminal attributes. In particular, there is no way to stop echoing or to change its concept of the interrupt and eof characters. rlogin seems to need -8 and, annoyingly, sets echo and onlcr. The latter can be fixed in your .rcrc: if ( ~ $TERM win ) { stty -echo -onlcr } win doesn't follow changes to the terminal attributes. In particular, there is no way to stop echoing or to change its concept of the interrupt and eof characters. WEdestroy messages aren't yet passed by wily. Thus, Del and Delcol can delete the window yet leave win running. There is a race condition; the user can press newline and then delete text before win has a chance to read it. AUTHOR
win was originally written by Gary Capell (gary@cs.su.oz.au). Alan Watson (alan@oldp.nmsu.edu) rewrote it and added support for arguments, pseudo-terminals instead of pipes, and execution of certain B2 commands by wily. The pseudo-terminal support in 9term, written by Matty Farrow (matty@cs.su.oz.au), was a great help. 1R1.1L1 of 1D1 win(1)
All times are GMT -4. The time now is 01:06 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy