Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1773
  • Last Modified:

setenv buffer limit in csh

It appears that there is a problem using setenv in csh. If I setenv on a variable and the data value is more than some amount of predefined characters (probably 1024), I get the following error from csh:  "Word too long."

Is there a way I can get around this problem ? The reason is that I have a file that I sourced. Inside this file is a number of setenv statements. After sourcing this file, the script calls up a GNU Makefile with those env. variables passed into it.
0
tbtran
Asked:
tbtran
1 Solution
 
Klaas082598Commented:
This seems to be a hardcoded limit in both csh and also in tcsh (a public domain (better) csh).
Sidenote: ksh and sh have no problems with longer than 1024 env var's. Maybe their limit is higher.
So one solution could be to rewrite everything to use sh or ksh.

But i don't understand the question completely:
If the setenv statements worked in the first
place, how can they not work lateron ?
What has make got to do with it ?
0
 
ahoffmannCommented:
This could also be a kernel parameter.
On IRIX 5.x you may change it with the systune command,
see man systune, parameter  nc_args.
On SunOS 4.x there is also a kernel parameter, but the kernel
must be rebuild to change it.
I'm not shure, but there was something similar on Solaris.
0

Featured Post

[Webinar On Demand] Database Backup and Recovery

Does your company store data on premises, off site, in the cloud, or a combination of these? If you answered “yes”, you need a data backup recovery plan that fits each and every platform. Watch now as as Percona teaches us how to build agile data backup recovery plan.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now