Hi,
I am new to unix. Is their a way to pass the output of the line below to a variable var1.
ls -1t | head -1.
I am trying something like var1=ls -1t | head -1, but I get error.
Situation is: I get file everyday through FTP in my unix box. I have to write a script that picks up first... (1 Reply)
I have a shell script which does the encryption of a file where i am passing the file name as a command line argument,but later on the script waits on the screen to enter Y or N
what is the command i should be using on the shell script
#!/bin/bash -x
outfilename=file.out
echo... (8 Replies)
Hi all
I have got a file digits.data containing the following data
1 3 4
2 4 9
7 3 1
7 3 10
I am writing a script that will pass an argument from C-shell to nawk command. But it seems the values in the nawk comman does not get set. the program does not print no values out. Here is the... (1 Reply)
Hi,
I am facing a problem to pass command line arguments that looks like
<script name> aa bb "cc" dd "ee"
I want to pass all 5 elements include the " (brackets). when I print the @ARGV the " disappear. I hope I explain myself
Regards,
Ziv (4 Replies)
Hi,
I have a very small requirement where i need to pass command output as an argument while invoking the shell script..
I need to call like this
sh testscript.sh ' ls -t Appl*and*abc* | head -n 1'
This will list one file name as ana argument..
I will be using "$1" in the shell... (2 Replies)
Hello all,
New to C and I'm trying to write a program which can run a unix command. Would like to have the option of giving the user the ability to enter arguments e.g for "ls" be able to run "ls -l".
I would appreciate any help.
Thanks
#include <stdio.h>
#include <unistd.h>
#include... (3 Replies)
Hi,
I'm trying to pass the variable in the find command like below
a=log.20111114
find /apps/file3_logs/env3/ -name '$a' -exec ls -lrt {} \;
but it's not working
thanks in advance.
Regards
Thelak (3 Replies)
Hi.
I'm trying to do a "simple" thing.
grep -rls grepped_exp path | xgs
where xgs is an alias to something like:
xargs gvim -o -c ":g/grepped_exp"
now the problem is that I want to pass the "grepped_exp" to the piped alias.
I was able to do something like what I want without the... (4 Replies)
Hi All,
I am having command to run which will take argument as input file. Right now we are creating the input file by cat and executing the command
ftptransfer -i input file
cat >input file
file1
file2
cntrl +d
Is there a way I can do that in a single command like
... (1 Reply)
Discussion started by: arunkumar_mca
1 Replies
LEARN ABOUT SUSE
pfsinhdrgen
pfsinhdrgen(1) General Commands Manual pfsinhdrgen(1)NAME
pfsinhdrgen - Create a pfs stream with different exposures defined by hdrgen script.
SYNOPSIS
pfsinhdrgen <sample.hdrgen>
DESCRIPTION
This program reads files defined in given hdrgen script and outputs them in a PFS stream. Each frame has a tag BV with corresponding
brightness value (APEX standard). Larger BV corresponds to less exposure (darker image), necessary to capture a bright scene.
The generated PFS stream is to be used with photo-metric calibration software and with generators of HDR images.
HDRGEN script file is a plain text file in which each line contains: <path_to_an_image> <inverse_of_exposure_time_in_seconds> <aper-
ture_size> <iso_speed> 0
In most cases it is convenient to use the jpeg2hdrgen program to create such a file automatically. In case it could not parse the exif
information from jpeg files, it is necessary to create this file by hand. Below are the sample contents of such file:
<--- cut here: sample.hdrgen /var/tmp/images/img08.jpg 4 2.8 100 0 /var/tmp/images/img09.jpg 58.8235 2.8 100 0 /var/tmp/images/img10.jpg
76.9231 2.8 100 0 /var/tmp/images/img11.jpg 322.581 2.8 100 0 /var/tmp/images/img12.jpg 400 2.8 100 0 <--- cut here: sample.hdrgen
EXAMPLES
pfsinhdrgen sample.hdrgen | pfsview
View exposures defined in sample.hdrgen script.
SEE ALSO jpeg2hdrgen(1)pfshdrcalibrate(1)BUGS
Please report bugs and comments on implementation to Grzegorz Krawczyk <gkrawczyk@users.sourceforge.net>.
pfsinhdrgen(1)
02-15-2013
, (NB: does not apply to potentially destructive commands)