• Home
  • Disclaimer
  • Contact
  • Archives
  • About
  • Subscribe
  • Support
  • Advertise

Kernel Talks

Unix, Linux, & Cloud!

  • How-to guides
    • Howto
    • Disk management
    • Configurations
    • Troubleshooting
  • OS
    • HPUX
    • Linux
  • Miscellaneous
    • Software & Tools
    • Cloud Services
    • System services
    • Virtualization
  • Certification Preparations
    • AWS Certified Solutions Architect – Associate
    • AWS Certified Solutions Architect – Professional
    • AWS Certified SysOps Administrator – Associate
    • AWS Certified Cloud Practitioner
    • Certified Kubernetes Administrator
    • Hashicorp Certified Terraform Associate
    • Oracle Cloud Infrastructure Foundations 2020 – Associate
  • Tips & Tricks
  • Linux commands
You are here: Home / Troubleshooting Errors

How to resolve setenv: command not found

Published: May 15, 2018 | Modified: June 24, 2020



setenv is a built-in command for csh. You need to have C Shell to tackle with setenv: command not found error.

setenv: command not found resolution

Error :

Set environment command setenv is not available on the system. You see below error :

root@kerneltalks # setenv
-bash: setenv: command not found

So question is how to install setenv command.

Solution :

setenv is a shell built-in command comes with C shell csh. Above error could be due to two things –

  1. csh is not installed on server
  2. User havnt invoked csh shell

For point 1, go ahead and install csh package.

For point 2, Simply invoke csh shell by changing user login shell (usermod -s)  or use chsh command as below –

root@kerneltalks # chsh root
Changing shell for root.
New shell [/bin/bash]: /bin/csh
Shell changed.

And to change shell on the fly for your current logged-in session use below command –

root@kerneltalks # echo $0
bash
root@kerneltalks # csh
root@kerneltalks # echo $0
csh

Now, after csh shell availability if you run setenv, it runs smooth!

# setenv
REMOTEHOST=210.23.23.456
XDG_SESSION_ID=1
HOSTNAME=kerneltalks
HOST=kerneltalks
TERM=xterm
SHELL=/bin/bash
HISTSIZE=1000
GROUP=root
USER=root
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=01;05;37;41:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.axv=01;35:*.anx=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=01;36:*.au=01;36:*.flac=01;36:*.mid=01;36:*.midi=01;36:*.mka=01;36:*.mp3=01;36:*.mpc=01;36:*.ogg=01;36:*.ra=01;36:*.wav=01;36:*.axa=01;36:*.oga=01;36:*.spx=01;36:*.xspf=01;36:
HOSTTYPE=x86_64-linux
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin
MAIL=/var/spool/mail/root
PWD=/root
LANG=en_US.UTF-8
HISTCONTROL=ignoredups
HOME=/root
SHLVL=6
OSTYPE=linux
VENDOR=unknown
MACHTYPE=x86_64
LOGNAME=root
LESSOPEN=||/usr/bin/lesspipe.sh %s
_=/bin/csh
⇠ Previous article
Why ps output shows UID instead of username
Next article ⇢
Execute command at shutdown and boot in Suse Linux

Related stuff:

  • How to resolve 83h/80h error in HPUX
  • Issues while working on ELK stack
  • How to resolve aclocal: not found error in Ubuntu
  • networker service not starting
  • How to troubleshoot RPC: Port mapper failure – Timed out error
  • pvcreate error: Device /dev/xyz not found (or ignored by filtering).
  • device eth0 does not seem to be present, delaying initialization error on Linux VM
  • Failed to mount cd error in Zypper
  • mount.nfs: requested NFS version or transport protocol is not supported
  • How to resolve the fatal error: curses.h: No such file or directory
  • VMware tools not running after Linux kernel upgrade
  • check_mk error Cannot fetch deployment URL via curl error

Filed Under: Troubleshooting Errors Tagged With: how to install setenv command, setenv command not found resolution, setenv: command not found

If you like my tutorials and if they helped you in any way, then

  • Consider buying me a cup of coffee via paypal!
  • Subscribe to our newsletter here!
  • Like KernelTalks Facebook page.
  • Follow us on Twitter.
  • Add our RSS feed to your feed reader.

Share Your Comments & Feedback: Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Get fresh content from KernelTalks

  • Email
  • Facebook
  • RSS
  • Twitter

Get Linux & Unix stuff right into your mailbox. Subscribe now!

* indicates required

This work is licensed under a CC-BY-NC license · Privacy Policy
© Copyright 2016-2023 KernelTalks · All Rights Reserved.
The content is copyrighted to Shrikant Lavhate & can not be reproduced either online or offline without prior permission.