Sponsored Content
Top Forums Shell Programming and Scripting NFS Mount 16+ group Issue in AIX Post 302792919 by pinnacle on Thursday 11th of April 2013 10:29:05 AM
Old 04-11-2013
Quote:
Originally Posted by Corona688
I think you need <<newgrp1 not << newgrp1 but your idea is sound, yes.

Be sure to escape $'s with \ since they will substitue before the code is run otherwise.

Could you please explain how this thing will work technically without invoking new shell.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

NFS Mount Os400 to AIX

I am having an issue in one of my LPARs gettin a NFS mount between it, AIX and an Iseres LPAR, Os400. I get NFS Server xxxx not responding still trying. When I run the df commmand it says NFS Server xxxxx ok. Then shows the fs and then continiously puts out the about not responding error and the... (0 Replies)
Discussion started by: capeme
0 Replies

2. AIX

How to do a NFS mount from AIX to Linux?

How to do? Thanks (1 Reply)
Discussion started by: rainbow_bean
1 Replies

3. AIX

can not mount from aix client to linux nfs server

Hi, I am trying to mount a nfs folder from AIX client to Linux NFS Server, but I got the following error: # mount 128.127.11.121:/aix /to_be_del mount: 1831-010 server 128.127.11.121 not responding: RPC: 1832-018 Port mapper failure - RPC: 1832-008 Timed out mount: retrying... (1 Reply)
Discussion started by: victorcheung
1 Replies

4. AIX

NFS mount problems on AIX

Hi, I have two machines (AIX) each on a different VLAN. Need to mount a filesystem using nfs on the other one. When I export the nfs file system its a breeze. But when I try to mount it on the other machine the smitty command hangs on "running" and i get an OK from smitty but with this... (6 Replies)
Discussion started by: aixromeo
6 Replies

5. Shell Programming and Scripting

Issue with changing the permissions on an nfs mount

Hi All, I have an nfs share which I mounted to my linux machine as below. df -k output TSDapp-na-02:/vol/tsd_app_1/rn_jira 47185920 11663072 35522848 25% /opt/rn_jira I have no entry for this in my /etc/fstab. I did it by the following way. mount -t nfs... (2 Replies)
Discussion started by: Tuxidow
2 Replies

6. AIX

HACMP, NFS cross-mount problem. Can not move resource group

Hi, I'm new to HACMP. Currently I setup a cluster with nfs cross-mount follow this guide: kristijan.org NFS cross-mounts in PowerHA/HACMPMy cluster has two nodes: erp01 and erp02. I'm using nfs4 with filesystem for nfs is: /sapnfs Cluster start without problems. But I cannnot move RG (with... (3 Replies)
Discussion started by: giobuon
3 Replies

7. AIX

Enable large filesize option in NFS mount in AIX 4.3

Hi All, I have a NFS mount filesystem, however it is not supporting a creation of filesize greater than 2 GB in it, how can i enable the option (bf = true) in it. The AIX version is 4.3.2 Thanks in Advance!! (1 Reply)
Discussion started by: mad_man12
1 Replies

8. Red Hat

NFS-Mount issue

Hi, While i try to mount the NFS file system on the client linux server i am getting the error message as (4 Replies)
Discussion started by: gsiva
4 Replies

9. Red Hat

NFS mount issue

Hi Friends, My source server is HP and my destination is linux. I have to mount a dir thru nfs from source to destn. almost 8 servers i did the same thing and it is working fine but on the 9th server i can't able to mount. Everything i have did for nfs configuration.Even i can able to ping... (1 Reply)
Discussion started by: Mohamed Thamim
1 Replies

10. Red Hat

NFS mount issue

we are facing a weird NFS mount issue on one of the linux host , a NFS volume of 2.4TB is mounted in the linux host , but df only reports 131g , which exactly matches rootfilesytem size nfs mount filer_filer1:/vol/bug_test/q0 131G 116G 8.5G 94% /nas/bug_test root... (2 Replies)
Discussion started by: skamal4u
2 Replies
ICON(1) 						      General Commands Manual							   ICON(1)

NAME
icon - interpret or compile Icon programs SYNOPSIS
icont [ option ... ] file ... [ -x arg ... ] iconc [ option ... ] file ... [ -x arg ... ] DESCRIPTION
icont and iconc each convert an Icon source program into executable form. icont translates quickly and provides interpretive execution. iconc takes longer to compile but produces programs that execute faster. icont and iconc for the most part can be used interchangeably. This manual page describes both icont and iconc. Where there there are differences in usage between icont and iconc, these are noted. File Names: Files whose names end in .icn are assumed to be Icon source files. The .icn suffix may be omitted; if it is not present, it is supplied. The character - can be used to indicate an Icon source file given in standard input. Several source files can be given on the same command line; if so, they are combined to produce a single program. The name of the executable file is the base name of the first input file, formed by deleting the suffix, if present. stdin is used for source programs given in standard input. Processing: As noted in the synopsis above, icont and iconc accept options followed by file names, optionally followed by -x and arguments. If -x is given, the program is executed automatically and any following arguments are passed to it. icont: The processing performed by icont consists of two phases: translation and linking. During translation, each Icon source file is translated into an intermediate language called ucode. Two ucode files are produced for each source file, with base names from the source file and suffixes .u1 and .u2. During linking, the one or more pairs of ucode files are combined to produce a single icode file. The ucode files are deleted after the icode file is created. Processing by icont can be terminated after translation by the -c option. In this case, the ucode files are not deleted. The names of .u1 files from previous translations can be given on the icont command line. These files and the corresponding .u2 files are included in the linking phase after the translation of any source files. The suffix .u can be used in place of .u1; in this case the 1 is supplied auto- matically. Ucode files that are explicitly named are not deleted. iconc: The processing performed by iconc consists of two phases: code generation and compilation and linking. The code generation phase produces C code, consisting of a .c and a .h file, with the base name of the first source file. These files are then compiled and linked to produce an executable binary file. The C files normally are deleted after compilation and linking. Processing by iconc can be terminated after code generation by the -c option. In this case, the C files are not deleted. OPTIONS
The following options are recognized by icont and iconc: -c Stop after producing intermediate files and do not delete them. -e file Redirect standard error output to file. -f s Enable full string invocation. -o name Name the output file name. -s Suppress informative messages. Normally, both informative messages and error messages are sent to standard error output. -t Arrange for &trace to have an initial value of -1 when the program is executed and for iconc enable debugging features. -u Issue warning messages for undeclared identifiers in the program. -v i Set verbosity level of informative messages to i -E Direct the results of preprocessing to standard output and inhibit further processing. The following additional options are recognized by iconc: -f string Enable features as indicated by the letters in string: a all, equivalent to delns d enable debugging features: display(), name(), variable(), error trace back, and the effect of -f n (see below) e enable error conversion l enable large-integer arithmetic n produce code that keeps track of line numbers and file names in the source code s enable full string invocation -n string Disable specific optimizations. These are indicated by the letters in string: a all, equivalent to cest c control flow optimizations other than switch statement optimizations e expand operations in-line when reasonable (keywords are always put in-line) s optimize switch statements associated with operation invocations t type inference -p arg Pass arg on to the C compiler used by iconc -r path Use the run-time system at path, which must end with a slash. -C prg Have iconc use the C compiler given by prg ENVIRONMENT VARIABLES
When an Icon program is executed, several environment variables are examined to determine certain execution parameters. Values in paren- theses are the default values. BLKSIZE (500000) The initial size of the allocated block region, in bytes. COEXPSIZE (2000) The size, in words, of each co-expression block. DBLIST The location of data bases for iconc to search before the standard one. The value of DBLIST should be a blank-separated string of the form p1 p2 ... pn where the pi name directories. ICONCORE If set, a core dump is produced for error termination. ICONX The location of iconx, the executor for icode files, is built into an icode file when it is produced. This location can be overridden by setting the environment variable ICONX. If ICONX is set, its value is used in place of the location built into the icode file. IPATH The location of ucode files specified in link declarations for icont. IPATH is a blank-separated list of directories. The current directory is always searched first, regardless of the value of IPATH. LPATH The location of source files specified in preprocessor $include directives and in link declarations for iconc. LPATH is otherwise sim- ilar to IPATH. MSTKSIZE (10000) The size, in words, of the main interpreter stack for icont. NOERRBUF By default, &errout is buffered. If this variable is set, &errout is not buffered. QLSIZE (5000) The size, in bytes, of the region used for pointers to strings during garbage collection. STRSIZE (500000) The initial size of the string space, in bytes. TRACE The initial value of &trace. If this variable has a value, it overrides the translation-time -t option. FILES
icont Icon translator iconc Icon compiler iconx Icon executor SEE ALSO
The Icon Programming Language, Ralph E. Griswold and Madge T. Griswold, Prentice-Hall Inc., Englewood Cliffs, New Jersey, Second Edition, 1990. Version 9.1 of Icon, Ralph E. Griswold, Clinton L. Jeffery, and Gregg M. Townsend, IPD267, Department of Computer Science, The University of Arizona, 1995. Version 9 of the Icon Compiler, Ralph E. Griswold, IPD237, Department of Computer Science, The University of Arizona, 1995. icon_vt(1) LIMITATIONS AND BUGS
The icode files for the interpreter do not stand alone; the Icon run-time system (iconx) must be present. Stack overflow is checked using a heuristic that is not always effective. 1 November 1995 IPD244b ICON(1)
All times are GMT -4. The time now is 01:20 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy