Sponsored Content
Top Forums UNIX for Dummies Questions & Answers file with executable permission Post 10109 by LivinFree on Thursday 8th of November 2001 02:22:48 AM
Old 11-08-2001
Well, if you're going to do that, I would recommend that you add the "." at the <b>end</b> of your PATH. You can add something like this to the end of your login script:
Code:
PATH="${PATH}:."

It is a little more secure this way...

One note:
If you are the superuser (root), it is not recommended to add the current directory to your path! You might end up running something you didn't mean to run.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Newbie question about difference between executable file and ordinary file

Hi, I am newbie in unix and just started learning it. I want to know what is the difference between an executable file and a file (say text file). How to create executable file? What is the extension for that? How to differentiate ? How does it get executed? Thanks (1 Reply)
Discussion started by: Balaji
1 Replies

2. Programming

update executable file

Hi All, Is it possible to update an executable file created using cc or gcc compiler. ie., very clearly If i create a C program and execute it and an executable file a.out is created. but the run time for the execution is around 30 minutes. Is it possible to update that executable, if some... (3 Replies)
Discussion started by: anent
3 Replies

3. Shell Programming and Scripting

Executable file

Hi everybody: I have strange problem. I have compiled a source code and created an executable file. This file I can use it into my PC, but when I copy this executable to my laptop this one doesn't work and the system tell me: bash: ./sbdart_unix: cannot execute binary file Somebody can... (3 Replies)
Discussion started by: tonet
3 Replies

4. AIX

Making Executable File

Hi All: I am a newbie. I have shell script and bunch of java jar files and I want to give one single executable file (may be .bin). Ex: I have test.sh, jar1.jar, jar2.jar. I have to make process.xxx When we run "process.xxx" it will run the "test.sh" script which inturn uses jar1.jar and... (0 Replies)
Discussion started by: laxman123
0 Replies

5. Programming

Running an executable file

I've created a c program and compiled it with gcc, in unix. The file name is abc.c and it is run by typing the command ./abc I have another program which creates a child process, and I need this abc program to run on that child process. I've tried execvp(), but it doesn't work. How can I run... (2 Replies)
Discussion started by: sdsd
2 Replies

6. UNIX for Advanced & Expert Users

How can i read a non text file in unix - ELF-64 executable object file - IA64

The binary file is ELF-64 executable object file - IA64. How i know that the source is Is there any comamnd in unix i can read these kind of files or use a thirty party software? Thanks for your help (8 Replies)
Discussion started by: alexcol
8 Replies

7. Shell Programming and Scripting

executable file

Hi, I want to know that how can i read the content of a .exe file?? Thanks (1 Reply)
Discussion started by: ss_ss
1 Replies

8. Programming

Executable file in C

Hi all, I have modified a C file and executed it. While executing the executable file for that C file, it shows à is cannot be printed. I have given isprint(à) to test it. When I copy the old executable file and execute it it shows it can be printed. Then I retain the C code back and executed it... (1 Reply)
Discussion started by: sivakumar.rj
1 Replies

9. Solaris

file just loaded does not appear to be executable

Hi When i m trying the boot the system with Primary HDD (c1t0d0s0) -- its solaris 10 I m getting an error "file just loaded does not appear to be executable".....So will anyone share the steps to recover from this stage I also tried to build the corrupted superblock from below command but... (0 Replies)
Discussion started by: taruntan
0 Replies

10. Solaris

Executable file on Solaris

Hi! What are executable file formats in Solaris? Can someone please share it? Thanks! (3 Replies)
Discussion started by: Klyde
3 Replies
SU(1)								   User Commands							     SU(1)

NAME
su - change user ID or become superuser SYNOPSIS
su [options] [username] DESCRIPTION
The su command is used to become another user during a login session. Invoked without a username, su defaults to becoming the superuser. The optional argument - may be used to provide an environment similar to what the user would expect had the user logged in directly. Additional arguments may be provided after the username, in which case they are supplied to the user's login shell. In particular, an argument of -c will cause the next argument to be treated as a command by most command interpreters. The command will be executed by the shell specified in /etc/passwd for the target user. You can use the -- argument to separate su options from the arguments supplied to the shell. The user will be prompted for a password, if appropriate. Invalid passwords will produce an error message. All attempts, both valid and invalid, are logged to detect abuse of the system. The current environment is passed to the new shell. The value of $PATH is reset to /bin:/usr/bin for normal users, or /sbin:/bin:/usr/sbin:/usr/bin for the superuser. This may be changed with the ENV_PATH and ENV_SUPATH definitions in /etc/login.defs. A subsystem login is indicated by the presence of a "*" as the first character of the login shell. The given home directory will be used as the root of a new file system which the user is actually logged into. OPTIONS
The options which apply to the su command are: -c, --command COMMAND Specify a command that will be invoked by the shell using its -c. The executed command will have no controlling terminal. This option cannot be used to execute interactive programs which need a controlling TTY. -, -l, --login Provide an environment similar to what the user would expect had the user logged in directly. When - is used, it must be specified before any username. For portability it is recommended to use it as last option, before any username. The other forms (-l and --login) do not have this restriction. -s, --shell SHELL The shell that will be invoked. The invoked shell is chosen from (highest priority first): The shell specified with --shell. If --preserve-environment is used, the shell specified by the $SHELL environment variable. The shell indicated in the /etc/passwd entry for the target user. /bin/sh if a shell could not be found by any above method. If the target user has a restricted shell (i.e. the shell field of this user's entry in /etc/passwd is not listed in /etc/shells), then the --shell option or the $SHELL environment variable won't be taken into account, unless su is called by root. -m, -p, --preserve-environment Preserve the current environment, except for: $PATH reset according to the /etc/login.defs options ENV_PATH or ENV_SUPATH (see below); $IFS reset to "<space><tab><newline>", if it was set. If the target user has a restricted shell, this option has no effect (unless su is called by root). Note that the default behavior for the environment is the following: The $HOME, $SHELL, $USER, $LOGNAME, $PATH, and $IFS environment variables are reset. If --login is not used, the environment is copied, except for the variables above. If --login is used, the $TERM, $COLORTERM, $DISPLAY, and $XAUTHORITY environment variables are copied if they were set. Other environments might be set by PAM modules. CAVEATS
This version of su has many compilation options, only some of which may be in use at any particular site. CONFIGURATION
The following configuration variables in /etc/login.defs change the behavior of this tool: CONSOLE_GROUPS (string) List of groups to add to the user's supplementary groups set when logging in on the console (as determined by the CONSOLE setting). Default is none. Use with caution - it is possible for users to gain permanent access to these groups, even when not logged in on the console. DEFAULT_HOME (boolean) Indicate if login is allowed if we can't cd to the home directory. Default is no. If set to yes, the user will login in the root (/) directory if it is not possible to cd to her home directory. ENV_PATH (string) If set, it will be used to define the PATH environment variable when a regular user login. The value is a colon separated list of paths (for example /bin:/usr/bin) and can be preceded by PATH=. The default value is PATH=/bin:/usr/bin. ENV_SUPATH (string) If set, it will be used to define the PATH environment variable when the superuser login. The value is a colon separated list of paths (for example /sbin:/bin:/usr/sbin:/usr/bin) and can be preceded by PATH=. The default value is PATH=/sbin:/bin:/usr/sbin:/usr/bin. SULOG_FILE (string) If defined, all su activity is logged to this file. SU_NAME (string) If defined, the command name to display when running "su -". For example, if this is defined as "su" then a "ps" will display the command is "-su". If not defined, then "ps" would display the name of the shell actually being run, e.g. something like "-sh". SYSLOG_SU_ENAB (boolean) Enable "syslog" logging of su activity - in addition to sulog file logging. FILES
/etc/passwd User account information. /etc/shadow Secure user account information. /etc/login.defs Shadow password suite configuration. EXIT VALUES
On success, su returns the exit value of the command it executed. If this command was terminated by a signal, su returns the number of this signal plus 128. If su has to kill the command (because it was asked to terminate, and the command did not terminate in time), su returns 255. Some exit values from su are independent from the executed command: 0 success (--help only) 1 System or authentication failure 126 The requested command was not found 127 The requested command could not be executed SEE ALSO
login(1), login.defs(5), sg(1), sh(1). shadow-utils 4.5 01/25/2018 SU(1)
All times are GMT -4. The time now is 04:22 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy