• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

can someone help me understand setting up the environment in Unix?

R

rasczak

Lifer
I am working on a project where 90% of the time I am working with Unix boxes (solaris 10)

I am confused by setting up the environment. all of the utilities I have needed thus far was sudo, so i mapped that to my .bashrc file as PATH=$PATH:/opt/sfw/bin

but now i need to map some tools located in another directory called /tools/system/cshrc.

I am so confused i can't even spell correctly right now. I thought it was set path but i am now being told to source it to that path. I wish I just knew what it meant to do that and how to do it.

Sheesh, learning this stuff is like riding a roller caoster.
 
"sourcing" a file is a way to read the contents of the file into the current shell. If you have a shell script that sets a bunch of variables and you just run it normally the variables will only affect the subshell that gets spawned and when the script exits your shell will be the same as it was before. If you source the script '. scriptname.sh' it'll all happen in the current shell instead of spawning a new one.
 
sweet! thanks guys! worked like a charm. nothinman, thanks for the explanantion, i am beginning to understand this a little bit better.
 
new issue I open a terminal and sudo su to root
I cd to /usr/bin/nsr
./nwarchive

and it won't open stating

XLIB connection refused by "server:0.0"

ideas?

I do not understand this whole DISPLAY thing at all.

in BASH

DISPLAY=server:0.0

I am doing something incorrectly, but I cannot figure it out for the life of me.
 
XLIB connection refused by "server:0.0"
Click to expand...

That X server didn't let you connect to it. You probably need to use xhost on an already authorized machine to allow that machine to connect. If you're running that locally you might want to try setting DISPLAY to :0, I'm not sure if it makes a difference without the hostname but it couldn't hurt to try.
 
sudo su - the mius was the problem for me. I didn't realize that when I added the minus sign, it inherits the environment of the user i am switching to as opposed to the original environment.

thanks for the help!
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top