Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Unable to run files with 700-777 permissions Post 302887213 by alister on Thursday 6th of February 2014 10:56:22 AM
Old 02-06-2014
Quote:
Originally Posted by wisecracker
Read your error report...
You need the absolute path...
Code:
/bin/32/bitcoin-qt*

The original ls is using a relative path. Using the absolute path you suggest will lead to a different directory if the current working directory of the relative path is anything other than /.


Quote:
Originally Posted by Corona688
It does not know where to find the file, because it does not search from the current path for security reasons.

To tell it to search from the current path, prefix the filename with ./
This is not a PATH issue, since PATH is not used when the command name contains slashes.

Regards,
Alister
This User Gave Thanks to alister For This Post:
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

How to run my own FTP server without root permissions

Hi all, I need your help with this problem. I have my own ftp server implemented in java. If I start it as root it is successfully binded to port 21 and everything works. Now I want to run it as non-root user, but for binding to port 21 it needs root rights. How to solve it? I alrady try... (3 Replies)
Discussion started by: giorgione
3 Replies

2. Shell Programming and Scripting

unable to run a script

thi is (10 Replies)
Discussion started by: angelina
10 Replies

3. Solaris

Unable to run xclock

Hello. I am trying to run xclock on newly built solaris box - These are the steps I followed: # DISPLAY=localhost:0.0 # export DISPLAY # xclock xclock: not found # cd /usr/openwin/bin # ./xclock Error: Can't open display: localhost:0.0 # Please suggest, what am i doing wrong? Thank... (27 Replies)
Discussion started by: panchpan
27 Replies

4. Shell Programming and Scripting

find and tar 700 files

i have some 700 files of the same pattern differing only in their datestamp. below some of the files. i want to tar them all into one tar file.but the below normal command is telling me "arg list too long" tar -cvf Archive1.tar CurrentCollectorMeterReadBackup* also i tried the below... (6 Replies)
Discussion started by: ali560045
6 Replies

5. Cybersecurity

can another user 777 and existing 777 dirctory?

User usrA creates dirA directory and runs chmod 777 on the directory. Can usrB issue another 777 on dirA? It appears the answer is no even if the usrA and usrB are part of the same group. I know this is a rare scenario but I just ran across it and found out that usrB receives an error when... (4 Replies)
Discussion started by: zlek131
4 Replies

6. Cybersecurity

Unable to run 'su' and 'sudo' after changing permissions on /etc

Hello, I'm running rhel6 64bit. Accidentally I ran % chmod -R 777 /etc and after that I have a problem to do 'su' or 'sudo'. When I did sudo it complained that /etc/sudoers has 777 while it should be 0440. I changed that and also restored right permission for: -rw-r--r-- 1 root root 1966 May 19... (2 Replies)
Discussion started by: susja
2 Replies

7. Shell Programming and Scripting

777 files and dir

i have four files that have 777 permission find /var/tttt/ -type f -perm 0777 /var/ttt/1 /var/ttt/2 /var/ttt/3 /var/ttt/4 if any file other than above 4 have 777 permission then move that file to /garbage/yyyy-mmm-dd . Also email me that this have abcd have 777 permission. (6 Replies)
Discussion started by: learnbash
6 Replies

8. AIX

find command to list all the 777 files and directories owned by root user

Hi I'm logged in to an AIX box now and we need to do an audit on this box. cbssapr01:# pwd / Which command will show all the files and directories owned by root user with permissions as 777 ? (8 Replies)
Discussion started by: newtoaixos
8 Replies

9. Solaris

Unable to delete directory even with 777 perm

Hi, I have an 'empty' directory 'tmp' of which I am the owner and 777 permission. But when I try to delete the directory using rmdir or rm command, it gives error. Command prompt snapshot: => uname SunOS ... (4 Replies)
Discussion started by: platinum81
4 Replies

10. Solaris

Permissions to run ZFS Snapshots

Hi, I work as an Oracle Technical consultant (mainly DBA related), and I have used ZFS snapshots on previous projects which has helped me a great deal. I often take snapshots before doing some dev work, and then I can roll it back if I want to start again, or if it goes pear shaped!! I have... (4 Replies)
Discussion started by: AndyG
4 Replies
filename(n)						       Tcl Built-In Commands						       filename(n)

__________________________________________________________________________________________________________________________________________________

NAME
filename - File name conventions supported by Tcl commands _________________________________________________________________ INTRODUCTION
All Tcl commands and C procedures that take file names as arguments expect the file names to be in one of three forms, depending on the current platform. On each platform, Tcl supports file names in the standard forms(s) for that platform. In addition, on all platforms, Tcl supports a Unix-like syntax intended to provide a convenient way of constructing simple file names. However, scripts that are intended to be portable should not assume a particular form for file names. Instead, portable scripts must use the file split and file join com- mands to manipulate file names (see the file manual entry for more details). PATH TYPES
File names are grouped into three general types based on the starting point for the path used to specify the file: absolute, relative, and volume-relative. Absolute names are completely qualified, giving a path to the file relative to a particular volume and the root directory on that volume. Relative names are unqualified, giving a path to the file relative to the current working directory. Volume-relative names are partially qualified, either giving the path relative to the root directory on the current volume, or relative to the current directory of the specified volume. The file pathtype command can be used to determine the type of a given path. PATH SYNTAX
The rules for native names depend on the value reported in the Tcl array element tcl_platform(platform): mac On Apple Macintosh systems, Tcl supports two forms of path names. The normal Mac style names use colons as path separators. Paths may be relative or absolute, and file names may contain any character other than colon. A leading colon causes the rest of the path to be interpreted relative to the current directory. If a path contains a colon that is not at the beginning, then the path is interpreted as an absolute path. Sequences of two or more colons anywhere in the path are used to construct relative paths where :: refers to the parent of the current directory, ::: refers to the parent of the parent, and so forth. In addition to Macintosh style names, Tcl also supports a subset of Unix-like names. If a path contains no colons, then it is interpreted like a Unix path. Slash is used as the path separator. The file name . refers to the current directory, and .. refers to the parent of the current directory. However, some names like / or /.. have no mapping, and are interpreted as Macin- tosh names. In general, commands that generate file names will return Macintosh style names, but commands that accept file names will take both Macintosh and Unix-style names. The following examples illustrate various forms of path names: : Relative path to the current folder. MyFile Relative path to a file named MyFile in the current folder. MyDisk:MyFile Absolute path to a file named MyFile on the device named MyDisk. :MyDir:MyFile Relative path to a file name MyFile in a folder named MyDir in the current folder. ::MyFile Relative path to a file named MyFile in the folder above the current folder. :::MyFile Relative path to a file named MyFile in the folder two levels above the current folder. /MyDisk/MyFile Absolute path to a file named MyFile on the device named MyDisk. ../MyFile Relative path to a file named MyFile in the folder above the current folder. unix On Unix platforms, Tcl uses path names where the components are separated by slashes. Path names may be relative or absolute, and file names may contain any character other than slash. The file names . and .. are special and refer to the current direc- tory and the parent of the current directory respectively. Multiple adjacent slash characters are interpreted as a single sepa- rator. The following examples illustrate various forms of path names: / Absolute path to the root directory. /etc/passwd Absolute path to the file named passwd in the directory etc in the root directory. . Relative path to the current directory. foo Relative path to the file foo in the current directory. foo/bar Relative path to the file bar in the directory foo in the current directory. ../foo Relative path to the file foo in the directory above the current directory. windows On Microsoft Windows platforms, Tcl supports both drive-relative and UNC style names. Both / and may be used as directory sep- arators in either type of name. Drive-relative names consist of an optional drive specifier followed by an absolute or relative path. UNC paths follow the general form \servernamesharenamepathfile, but must at the very least contain the server and share components, i.e. \servernamesharename. In both forms, the file names . and .. are special and refer to the current directory and the parent of the current directory respectively. The following examples illustrate various forms of path names: \Hostshare/file Absolute UNC path to a file called file in the root directory of the export point share on the host Host. Note that repeated use of file dirname on this path will give //Host/share, and will never give just /fB//Host/fR. c:foo Volume-relative path to a file foo in the current directory on drive c. c:/foo Absolute path to a file foo in the root directory of drive c. fooar Relative path to a file bar in the foo directory in the current directory on the current volume. foo Volume-relative path to a file foo in the root directory of the current volume. \foo Volume-relative path to a file foo in the root directory of the current volume. This is not a valid UNC path, so the assumption is that the extra backslashes are superfluous. TILDE SUBSTITUTION
In addition to the file name rules described above, Tcl also supports csh-style tilde substitution. If a file name starts with a tilde, then the file name will be interpreted as if the first element is replaced with the location of the home directory for the given user. If the tilde is followed immediately by a separator, then the $HOME environment variable is substituted. Otherwise the characters between the tilde and the next separator are taken as a user name, which is used to retrieve the user's home directory for substitution. The Macintosh and Windows platforms do not support tilde substitution when a user name follows the tilde. On these platforms, attempts to use a tilde followed by a user name will generate an error that the user does not exist when Tcl attempts to interpret that part of the path or otherwise access the file. The behaviour of these paths when not trying to interpret them is the same as on Unix. File names that have a tilde without a user name will be correctly substituted using the $HOME environment variable, just like for Unix. PORTABILITY ISSUES
Not all file systems are case sensitive, so scripts should avoid code that depends on the case of characters in a file name. In addition, the character sets allowed on different devices may differ, so scripts should choose file names that do not contain special characters like: <>:"/|. The safest approach is to use names consisting of alphanumeric characters only. Also Windows 3.1 only supports file names with a root of no more than 8 characters and an extension of no more than 3 characters. On Windows platforms there are file and path length restrictions. Complete paths or filenames longer than about 260 characters will lead to errors in most file operations. KEYWORDS
current directory, absolute file name, relative file name, volume-relative file name, portability SEE ALSO
file(n), glob(n) Tcl 7.5 filename(n)
All times are GMT -4. The time now is 05:57 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy