08-30-2011
Thanks for your reply. We need to change from BASH to KSH with in the same script. Reason being some of the environment related settings are done using BASH.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi Buddy,
Can any one help me to overcome from the below problem?
#/usr/bin/ksh
typeset -Z dd
dd=1
echo $dd
===========
out put for the above is 01
same script I'm migrating to bash but typeset -Z option is not found in bash, Pls get me the equivalent option in BASH
Thanks in... (1 Reply)
Discussion started by: krishna
1 Replies
2. Shell Programming and Scripting
Hello,
I've written a script in KSH, but now it needs to run on a system without KSH, ie sh or bash etc, bash seems best bet, but the simplest of things don't seem to work..
The snippet below is the main issue, basically I'm reading from a dat file and putting fields into arrays..
Dat file... (5 Replies)
Discussion started by: itsupplies
5 Replies
3. Shell Programming and Scripting
Hi,
I use AIX (ksh) and Linux (bash) servers. I'm trying to do scripts to will run in both ksh and bash, and most of the time it works. But this time I don't get it in bash (I'm more familar in ksh).
The goal of my script if to read a "config file" (like "ini" file), and make various report.... (2 Replies)
Discussion started by: estienne
2 Replies
4. Shell Programming and Scripting
Hi guys...
I have a ksh shell by default, so when I login to my unix box, all my .profile statements gets executed(including the aliases).
But for some reasons(may be not comfortable using ksh), I would always switch to BASH(in the same session but as a child process) but in the process I am... (16 Replies)
Discussion started by: anduzzi
16 Replies
5. UNIX for Dummies Questions & Answers
Hi,
I am a new bie to unix shell programming. I have specified ksh as the first line in my script but when executed it complains.
*********** Script=test********************
#!/usr/bin/ksh
echo hello
print -p 123
************************************
++++++++ Execution... (7 Replies)
Discussion started by: akhilnagpal
7 Replies
6. Solaris
Hi,
I've a general question regarding shell. I 've seen that every where i worked in production environment people are using ksh .. but i like to use .. bash .. is there any particular reason why hardcore sysadmins use ksh ? (8 Replies)
Discussion started by: fugitive
8 Replies
7. UNIX for Dummies Questions & Answers
I'm a user on a fairly locked down sys V server. By default, I have ksh set as my default shell. I added to my .profile:
bash -o vi
so when I login, it goes into bash so I can take advantage of tab completion and use the up key to bring up previous commands. However, whenever I want to exit, I... (2 Replies)
Discussion started by: mrwatkin
2 Replies
8. Shell Programming and Scripting
what is diff between KSH and Bash can you tell me some commands which run in either of two but not in both.
while doing normal shell programming I am unable to find diffrence between two (2 Replies)
Discussion started by: pasricha.kunal
2 Replies
9. Shell Programming and Scripting
Hi all
Below code works in bash but it is not working in ksh.
enddate=`date -d "$enddate + $i day" "+%Y_%m_%d"`
Please help me how it works in ksh
Thanks (10 Replies)
Discussion started by: pmreddy
10 Replies
10. Shell Programming and Scripting
Hello,
I want to run a script written in ksh but my default shell is bash as root e.g in the script it has #!/bin/ksh
i have gone into /etc/passwd to change it from :/bin/bash to /bin/ksh
but still giving me an error when running scripts such as ./installer
-bash: ./installer: /bin/ksh:... (3 Replies)
Discussion started by: DOkuwa
3 Replies
LEARN ABOUT LINUX
megaco_transport
megaco_transport(3erl) Erlang Module Definition megaco_transport(3erl)
NAME
megaco_transport - Megaco transport behaviour.
DESCRIPTION
The following functions should be exported from a megaco_transport callback module:
* send_message/2 [ mandatory ]
* send_message/3 [ optional ]
* resend_message/2 [ optional ]
*
EXPORTS
Module:send_message(Handle, Msg) -> ok | {cancel, Reason} | Error
Module:send_message(Handle, Msg, Resend) -> ok | {cancel, Reason} | Error
Types Handle = term()
Msg = binary() | iolist()
Resend = boolean()
Reason = term()
Error = term()
Send a megaco message.
If the function returns {cancel, Reason} , this means the transport module decided not to send the message. This is not an error. No
error messages will be issued and no error counters incremented. What actions this will result in depends on what kind of message
was sent.
In the case of requests, megaco will cancel the message in much the same way as if megaco:cancel had been called (after a success-
full send). The information will be propagated back to the user differently depending on how the request(s) where issued: For
requests issued using megaco:call , the info will be delivered in the return value. For requests issued using megaco:cast the info
will be delivered via a call to the callback function handle_trans_reply .
In the case of reply, megaco will cancel the reply and information of this will be returned to the user via a call to the callback
function handle_trans_ack .
The function send_message/3 will only be called if the resend_indication config option has been set to the value flag . The third
argument, Resend then indicates if the message send is a resend or not.
Module:resend_message(Handle, Msg) -> ok | {cancel, Reason} | Error
Types Handle = term()
Msg = binary() | iolist()
Reason = term()
Error = term()
Re-send a megaco message.
Note that this function will only be called if the user has set the resend_indication config option to true and it is in fact a mes-
sage resend. If not both of these condition's are meet, send_message will be called.
If the function returns {cancel, Reason} , this means the transport module decided not to send the message. This is not an error. No
error messages will be issued and no error counters incremented. What actions this will result in depends on what kind of message
was sent.
In the case of requests, megaco will cancel the message in much the same way as if megaco:cancel had been called (after a success-
full send). The information will be propagated back to the user differently depending on how the request(s) where issued: For
requests issued using megaco:call , the info will be delivered in the return value. For requests issued using megaco:cast the info
will be delivered via a call to the callback function handle_trans_reply .
In the case of reply, megaco will cancel the reply and information of this will be returned to the user via a call to the callback
function handle_trans_ack .
Ericsson AB megaco 3.15.1 megaco_transport(3erl)