Calling shell script within awk script throws error
I am getting the following error while passing parameter to a shell script called within awk script. Any idea what's causing this issue and how to ix it ? Thanks
sh: -c: line 0: syntax error near unexpected token `newline'
sh: -c: line 0: `./billdatecalc.sh <SetList>50/10000////D4B790E1////3/0</SetList>'
The "param" variable carries the following data "<SetList>50/10000////D4B790E1////3/0</SetList>"
I have a build script. It was created on Linux. For some reason, I got it to windows and modified it. And brought it back again to Linux.
Since there is the question of the ^M chars appearing, the way out is to do a dos2unix on the script file. This is done manually.
Is there a way to call... (4 Replies)
Hi all,
I have two ksh scripts
#sample1.sh
#!/bin/ksh
. ./sample2.sh
echo $fileExist
#sample2.sh
#!/bin/ksh
func()
{
i=1
return $a
}
func
echo $?
Here how should I return the value of sample2.sh back to sample1.sh?
Thanks in advance. (2 Replies)
Hi,
I am writing a script that needs to call a stored proc which would update a column in a table based on a condition.
I need to also capture the number of rows updated.
However, When I execute the script I keep getting this error:
./test_isql.sh: syntax error at line 33: `end of file'... (3 Replies)
hello everyone
i am beginner on shell scripting .and i am working on my project work on ad hoc network
i wrote a batch (.sh) to do a looping and execute a tcl script i wrote before in each iteration ..but i got this problem "
syntax error near unexpected token `('... (1 Reply)
HI,
We are using two shell scripts, script.sh,env.sh, where env.sh will be called inside script.sh. The variable inside env.sh is used as $var in script.sh.But while running the script its not identifying that variable. Is there any permission needed to call a script inside another script.
... (3 Replies)
Can someone let me know how could I achieve this
In one of per script I am calling the shell script but I need to so one thing that is one shell script call I need to pass pne argument.In below code I am calling my ftp script but here I want to pass one argument so how could I do this (e.g:... (5 Replies)
Hi,
I am working on a sever A.
I want to write a perl script to execute a shell script persent on the server B.
please help me in this.
thanks in advance. (3 Replies)
Hello there,
I am new to the awk scripting and getting the following error while running the script. Please can you advise me how to resolve this . Thanks
./sub_del_awk_lat.sh
awk: cmd. line:5: warning: escape sequence `\/' treated as plain `/'
awk: cmd. line:5: sed -n... (6 Replies)
Hi All,
I need to call a script in another server(Say B).So I logged in my local Machine(say A)using putty and given these command
ssh root@hostname
cd home\oracle
sh script.sh.
This is working perfectly.But when I have those command in a shell script and placed in my local... (2 Replies)
While I am trying to check the filename/s in IF statement of a shell script (RedHat Linux 6) I am getting below error:
File check:
filename_time2=`date --date='yesterday' +%Y-%m-%d`
cd /location/of/the/files/to/copy
if
then
cp server.log-$filename_time2* ../archive/new... (5 Replies)
Discussion started by: Dip
5 Replies
LEARN ABOUT HPUX
_lwp_setscheduler
_lwp_setscheduler(2) System Calls Manual _lwp_setscheduler(2)NAME
_lwp_setscheduler() - set LWP(Lightweight Process) scheduling policy and parameters
SYNOPSIS DESCRIPTION
The function allows the scheduling policy and parameters of an individual LWP in any process to be set. For and the only required member
of the sched_param structure is the priority sched_priority.
The cmd argument determines the action to be performed by the system call and supports one of the following values. Other values of cmd
are reserved for use by HP and may change without notice. The behavior of _lwp_setscheduler is undefined if any other value is passed to
the cmd argument and it may change without notice.
This request sets the scheduling policy and associated scheduling parameters
for the LWP whose LWP ID is specified by target_lwp to the policy and associated parameters provided in policy and param
respectively. The LWPID specified by target_lwp can be in any process. If the value of target_lwp is zero(0), the target
LWP will be the calling LWP.
This request sets the scheduling policy and associated scheduling parameters
for all LWPs in the target process specified by target_lwp to the policy and associated parameters provided in policy and
param, respectively. For this request, the PID value should be passed in the target_lwp parameter. The policy and param
arguments are stored in the process so they may be assigned to the child process during a fork operation.
If the function fails, no scheduling parameters or policies shall be changed for the specified LWP(s).
Appropriate privileges are required to change the scheduling parameters of another LWP. The calling LWP must have appropriate privileges
or be a member of a group having access to successfully call
Refer to the rtsched(2) manpage for a complete description of scheduling policies and priorities available. is similar to the function
except that it operates on lightweight processes instead of processes.
RETURN VALUE
Upon successful completion, returns with a value of 0; otherwise, it returns an error number to indicate the error. The variable is NOT
set if an error occurs.
ERRORS
For each of the following conditions, if the condition is detected, the function fails and returns the corresponding error number:
The target process could not be accessed due to compartmental restrictions.
The param parameter points to an illegal address.
The cmd parameter is invalid.
The value of the
policy parameter is invalid, or the param parameter is NULL, or one or more parameters contained in param is outside
the valid range for the specified scheduling policy.
The requesting LWP does not have permission to set the scheduling policy
and parameter for the specified LWP(s).
No LWP can be found corresponding to that specified by
target_lwp.
No process can be found corresponding to that specified by
target_lwp for the request.
WARNINGS
In general, the POSIX pthread interfaces should be used by multi-threaded applications. This system call may be used directly only when
the application has a need to operate on LWPs in another process. This system call may result in undefined behavior if the usage is mixed
with POSIX pthread APIs.
SEE ALSO _lwp_getscheduler(2), sched_setscheduler(2), pthread_setschedparam(3t).
_lwp_setscheduler(2)