02-13-2007
Try using "print -r" or "print -R" instead of just "print".
9 More Discussions You Might Find Interesting
1. HP-UX
hi
1).in the command "set" result, the 2nd line is
EDITOR=vi
is it means the vi editor is the default editor?
2). is "nedit"editor available in hpux 11iv2?
if no how to install or work in nedit in hpux 11i? (0 Replies)
Discussion started by: sekar sundaram
0 Replies
2. Shell Programming and Scripting
Hi Friends,
We have migrated our Unix from HP True 64 v5.1 to HP-UX B.11.11i recently and copied all my shell scripts ( Korn shell ) to new HP-UX B.11.11i unix machine. I've encountered lot of errors during execution of the scripts for example:
cat x.sh
#!/usr/bin/ksh
if
then
echo... (3 Replies)
Discussion started by: krishna
3 Replies
3. HP-UX
how i can enable backspace or charector deletion in hpux11i shell prompt. (12 Replies)
Discussion started by: jestinabel
12 Replies
4. HP-UX
As per the man page, pstat_getdisk() call returns the number of instances, which could be 0 upon successful completion, otherwise a value of -1 is returned.
Please have a look at this sample program ->
#include <stdio.h>
#include <sys/pstat.h>
int main()
{
int j = 0, ret;
struct... (2 Replies)
Discussion started by: sandiworld
2 Replies
5. HP-UX
I am new for HPUX OS and want to pursue my career in HPUX Administration.
I could not able to get following information from HP.com site, that why I need an assistance to know that - can I install HPUX 11i V3 OS on old HP B2000 & B1000 workstations (these workstation are 4 to 5 year old) or not,... (5 Replies)
Discussion started by: girish.batra
5 Replies
6. Shell Programming and Scripting
On a very new (11.31) hpux machine, I can no longer execute shell fragements like:
if ; then
. .profile.foo
fi
and get "ksh: test: argument expected"
if I convert this to -d or -f as appropriate (which I've not had to do on older versions of hpux (11.23) nor any other unix platform... (9 Replies)
Discussion started by: Peeter Joot
9 Replies
7. HP-UX
Wrote a KSH script on a RHEL server and moved it over to the HPUX server and it is not liking a loop that I put together. Here is the simple form of it that does not work in KSH:
for x in {0..$VARIABLE_NAME}
do
echo $x
done
This works:
for x in {0..10}
do
echo $x
... (3 Replies)
Discussion started by: jake0391
3 Replies
8. Shell Programming and Scripting
Hi all,
I have used a bash script which ultimately converts a string into date using date --date option:
DATE=$DATE" "$TIME" "`date +%Y` //concatenating 2 strings
TMRW_DATE=`date --date="$DATE" +"%s"` //applying date command on string and getting the unixtime
Please use code tags... (7 Replies)
Discussion started by: Rashu123
7 Replies
9. UNIX for Advanced & Expert Users
I think I discovered a bug in ksh.
$ cat test.sh
x=`echo hello | cat 2>&1 >/dev/null`
echo $x
y=`echo hello | cat >/dev/null 2>&1`
echo $y
works with all shells, including ksh in normal mode.
But does not work with ksh -x:
$ ksh -x test.sh
+ + echo hello
+ cat
+ 2>& 1 x=1> /dev/null
+... (11 Replies)
Discussion started by: MadeInGermany
11 Replies
print(9E) Driver Entry Points print(9E)
NAME
print - display a driver message on system console
SYNOPSIS
#include <sys/types.h>
#include <sys/errno.h>
#include <sys/ddi.h>
#include <sys/sunddi.h>
int prefixprint(dev_t dev, char *str);
INTERFACE LEVEL
Architecture independent level 1 (DDI/DKI). This entry point is required for block devices.
PARAMETERS
dev Device number.
str Pointer to a character string describing the problem.
DESCRIPTION
The print() routine is called by the kernel when it has detected an exceptional condition (such as out of space) in the device. To display
the message on the console, the driver should use the cmn_err(9F) kernel function. The driver should print the message along with any
driver specific information.
RETURN VALUES
The print() routine should return 0 for success, or the appropriate error number. The print routine can fail if the driver implemented a
non-standard print() routine that attempted to perform error logging, but was unable to complete the logging for whatever reason.
SEE ALSO
cmn_err(9F)
Writing Device Drivers
SunOS 5.10 15 Sep 1992 print(9E)