08-20-2009
Solaris 9 -- unable to set permanent PATH
Hi,
I've read forums far and wide trying to learn how to append to my PATH in Solaris 9 and every time I think I am close I discover my system is not configured the same. Its so frustrating because this all stems from a new server I am trying to setup identical to the production machine. (Of course I didn't configure the production box and on that machine it works how I want it).
So to recap what I am trying to accomplish.
In Solaris 9 add paths to the PATH env variable permanently; other words every time I start a ssh session switch to root I get the path and don't have to add it each time. And applications I start will continue to run with those env variables even after disconnect.
Other details:
My system doesn't utilize home directories, don't know why but they don't exist, not that this should matter since the prod box doesn't use them. I've looked in the /etc/default and /etc/login on the production machine but nothing matches the path I see when type "set" at the console. I've looked for .bashcrc and the .crsch files and I can't find them using "find" so I don't believe these are not the problem. I've also looked at the /etc/skel files but the path isn't there either. Last detail; the PATH I want that shows on prod machine only appears when logged in as root.
So from what I understand I've tried everything that has been posted. Now I am resorting to posting my own experience. I hope someone can help.
Thanks,
Thor
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello,
I just want to know ow I can set permanent pathes or whatever using setenv command. I'm using c shell .
regards,
me (1 Reply)
Discussion started by: geoquest
1 Replies
2. Solaris
Hi guys,
I'm running Solars 8 on a V100 server at home for testing.
If I switch user to root and do:
# echo $PATH
This is the output:
/usr/sbin:/usr/bin
I'm using rsync over ssh and need to add /usr/local/bin and /user/local/sbin.
I do this by running the line:
#... (3 Replies)
Discussion started by: Stin
3 Replies
3. AIX
I set my TERM variable to work with SMIT and everything works fine but when I logged out and log in again I have to set the variable again.
How can I set a permanent variable into the system so it will be as I wish even if a reboot is needed?
I set variables this way:
export VAR=value (7 Replies)
Discussion started by: agasamapetilon
7 Replies
4. Solaris
Hi,
I want to set the path for my application so I am setting the path as below --
PATH=${PATH}:.:/envs/mldev/tools:/envs/mldev/common/tools:${HOME}:/bin/p4v:/usr/j2se:/usr/j2se/bin:/usr/j2se/lib
or
PATH="\
/usr/bin:\
/usr/sbin:\
/usr/dt/bin:\
... (7 Replies)
Discussion started by: smartgupta
7 Replies
5. Solaris
how do I make sure that the entry in the routing table on Solaris 8 stay permanent after rebooting the server.
For example
route add 172.20.1.60 -netmask 255.255.255.0 172.20.255.253
Each time the server reboots the entry disappears when using the command netstat -nr (2 Replies)
Discussion started by: tv.praveenkumar
2 Replies
6. HP-UX
Hi all
I have a request from user to change the file descriptors limit to 8192. The current setting are:
root@xxxxx:(wmdev)> ulimit -a
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) 1048576
stack(kbytes) 131072
memory(kbytes) unlimited... (3 Replies)
Discussion started by: hedkandi
3 Replies
7. Solaris
Hi All
On my Solaris 10 X86, under my root directory I have a file called Aliases. It is owned by root (root:root) and the user (I mean root) has rwx permissions. In this file I have set some aliases like the following
alias a="cd /opt/IBM/WebSphere/AppAerver/Profiles"
When I run the above... (0 Replies)
Discussion started by: chrs0302
0 Replies
8. Shell Programming and Scripting
Hello All,
Hope you can understand my problem from the below code.
$ cat ~/.profile
PS1=`whoami`@`hostname`':$PWD
$ '
export PATH="$PATH:.:/logarchive/utility/util:/usr/sbin:"
$ echo $PATH
/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:.:/usr/sbin:
$ echo $SHELL
/usr/bin/ksh
... (6 Replies)
Discussion started by: sathyaonnuix
6 Replies
9. Shell Programming and Scripting
I'm trying to set path for the current session but it is not doing so.
It works perfectly on command line though.
#!/usr/bin/ksh
PATH=$PATH:/opt/quest/bin
Is there any specific way to set path on korn? (3 Replies)
Discussion started by: pjeedu2247
3 Replies
10. Shell Programming and Scripting
We are using csh on our AIX platform, if we have to export/set a specific environment variable we use setenv command but its only valid till session.
How do we set that variable permanent in our csh AIX? Do we put it in userprofile file or something else? (1 Reply)
Discussion started by: aixusrsys
1 Replies
LEARN ABOUT V7
systemd-machine-id-setup
SYSTEMD-MACHINE-ID-SETUP(1) systemd-machine-id-setup SYSTEMD-MACHINE-ID-SETUP(1)
NAME
systemd-machine-id-setup - Initialize the machine ID in /etc/machine-id
SYNOPSIS
systemd-machine-id-setup
DESCRIPTION
systemd-machine-id-setup may be used by system installer tools to initialize the machine ID stored in /etc/machine-id at install time, with
a provisioned or randomly generated ID. See machine-id(5) for more information about this file.
If the tool is invoked without the --commit switch, /etc/machine-id is initialized with a valid, new machined ID if it is missing or empty.
The new machine ID will be acquired in the following fashion:
1. If a valid D-Bus machine ID is already configured for the system, the D-Bus machine ID is copied and used to initialize the machine ID
in /etc/machine-id.
2. If run inside a KVM virtual machine and a UUID is configured (via the -uuid option), this UUID is used to initialize the machine ID.
The caller must ensure that the UUID passed is sufficiently unique and is different for every booted instance of the VM.
3. Similarly, if run inside a Linux container environment and a UUID is configured for the container, this is used to initialize the
machine ID. For details, see the documentation of the Container Interface[1].
4. Otherwise, a new ID is randomly generated.
The --commit switch may be used to commit a transient machined ID to disk, making it persistent. For details, see below.
Use systemd-firstboot(1) to initialize the machine ID on mounted (but not booted) system images.
OPTIONS
The following options are understood:
--root=root
Takes a directory path as argument. All paths operated will be prefixed with the given alternate root path, including the path for
/etc/machine-id itself.
--commit
Commit a transient machine ID to disk. This command may be used to convert a transient machine ID into a persistent one. A transient
machine ID file is one that was bind mounted from a memory file system (usually "tmpfs") to /etc/machine-id during the early phase of
the boot process. This may happen because /etc is initially read-only and was missing a valid machine ID file at that point.
This command will execute no operation if /etc/machine-id is not mounted from a memory file system, or if /etc is read-only. The
command will write the current transient machine ID to disk and unmount the /etc/machine-id mount point in a race-free manner to ensure
that this file is always valid and accessible for other processes.
This command is primarily used by the systemd-machine-id-commit.service(8) early boot service.
--print
Print the machine ID generated or committed after the operation is complete.
-h, --help
Print a short help text and exit.
--version
Print a short version string and exit.
EXIT STATUS
On success, 0 is returned, a non-zero failure code otherwise.
SEE ALSO
systemd(1), machine-id(5), systemd-machine-id-commit.service(8), dbus-uuidgen(1), systemd-firstboot(1)
NOTES
1. Container Interface
https://www.freedesktop.org/wiki/Software/systemd/ContainerInterface
systemd 237 SYSTEMD-MACHINE-ID-SETUP(1)