02-08-2013
Are you doing this as root? It may be a permission issue.
8 More Discussions You Might Find Interesting
1. Programming
Hello,
when i compile with xlc on aix i got the error message "ld: 0711-317 ERROR: Undefined symbol: .hello"
dummy.pc:
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include "dummy.h"
int main ( )
{
printf("\nbefore Hello");
hello();
printf("\npast Hello"); ... (2 Replies)
Discussion started by: stockdan
2 Replies
2. UNIX for Dummies Questions & Answers
hi there
i write one awk script file in shell programing
the code is related to dd/mm/yy to month, day year format
but i get an error
please can anybody help me out in this problem ??????
i give my code here including error
awk `
# date-month -- convert mm/dd/yy to month day,... (2 Replies)
Discussion started by: Herry
2 Replies
3. Red Hat
Dear All,
I am facing a unknown error, I start the Linux (RHEL 4 update 6) as usual.
After starting the various services(like network,sendmail,portmap etc) a error appears suddenly.
The error looks like :
Post_create: setxattr failed, rc=28 (dev=hda2 ino=772685)
Post_create: setxattr... (2 Replies)
Discussion started by: akhtar.bhat
2 Replies
4. Programming
I am trying to compile pro*c program on aix 5.3. The program compiled fine when I was using curses library. After switching to ncurses, I have started getting compilation errors. After installing ncurses on the box, I changed the -lcurses flag to -lncurses. I have also updated the path to the... (13 Replies)
Discussion started by: wvuguy
13 Replies
5. AIX
I am trying to build a code on IBM_AIX 5.3.
& getting error message as-
ld: 0711-736 ERROR: Input file $projdir/obj/ibm/5.3/new/new.o:
XCOFF64 object files are not allowed in 32-bit mode.
Error code return is 8.
Can anybody guide to resolve the error.
Thanks (5 Replies)
Discussion started by: milindb
5 Replies
6. UNIX for Advanced & Expert Users
Hi everyone, newbie forum poster here. I'm an Oracle DBA and I require some guidance from the Unix gurus here about how to pinpoint where a problem is within a Solaris 9 system running on an 8 CPU Fujitsu server that acts as our Oracle database server. Our sysadmins are trying their best to... (13 Replies)
Discussion started by: DBA_guy
13 Replies
7. Shell Programming and Scripting
Background
-------------
The Unix flavor can be any amongst Solaris, AIX, HP-UX and Linux. I have below 2 flat files.
File-1
------
Contains 50,000 rows with 2 fields in each row, separated by pipe.
Row structure is like Object_Id|Object_Name, as following:
111|XXX
222|YYY
333|ZZZ
... (6 Replies)
Discussion started by: Souvik
6 Replies
8. UNIX for Dummies Questions & Answers
im kinda new to shell scripting so i need some help
i try to run this script and get the error code
> 5 ")syntax error: operand expected (error token is "
the code for the script is
#!/bin/sh
#
# script to see if the given value is correct
#
# Define errors
ER_AF=86 # Var is... (4 Replies)
Discussion started by: metal005
4 Replies
nlspath(4) Kernel Interfaces Manual nlspath(4)
NAME
nlspath - NLSPATH configuration file
DESCRIPTION
The file allows the superuser to restrict the paths set by others through an environment variable to locate message catalogs for or root
programs.
This file contains only one entry with the following format:
pseudo-pathnames in this file should be absolute pathnames and must be separated by a colon. The paths which are available both in the
configuration file and environment variable are considered to locate message catalog files. The file should not be edited directly.
Instead, the command should be used to modify the contents of this file. See chnlspath(1M) for details.
If contains the file is in compatibility mode. In this case, all and root programs use the environment variable directly to locate message
catalogs. This configuration file is supported only to provide backward compatibility for those or root programs which are depending on
the environment variable New or root programs should not depend on the environment variable and configuration file
EXAMPLES
An entry in this file would typically look like:
WARNINGS
The configuration file must be root owned and there should not be write permission set for group and others. Superuser should not provide
write permission for group and others for the paths mentioned in the configuration file.
is provided only for compatibility with existing or root applications that make use of relative pathnames while invoking catopen(3C). New
or root applications must use absolute pathnames while invoking catopen(3C).
This file is to be obsoleted at a future date.
FILES
SEE ALSO
catopen(3C), chnlspath(1M), environ(5).
TO BE OBSOLETED nlspath(4)