Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

unable to more a file which I own

Status
Not open for further replies.

CooperS

Technical User
Aug 19, 2002
7
GB
On Solaris I am unable to more files which I own as userid snsnys. It goes back to the prompt without listing the contents.

I can only more the file if I log in as root.
If I do an ls -lrt I see

-rwxrwxrwx 1 snsnys staff 79640 Dec 16 09:34 xp1.txt*

I notice there is a star at the end of the file listing
I believe this means that I do not have access rights to the file. What can I do to be able to more the file? I have looked in Solaris admintool but I am not sure that this is the right application to use.
 
no, the start character at the end of the file name indicates that the file has execution permissio (it is an executable)

man ls to see more options.

is the file a text file? or is a binary file? if it is a text file, chmod -x xp1.txt and then more it.
 
Did your try 'more xp1.txt\*' ?

Try putting the backslash before the * and it will see it as a literal character instead of a wildcard.
 
start character at the end

sounds like an oxy-moron ;)

vlad
+----------------------------+
| #include<disclaimer.h> |
+----------------------------+
 
Also, 'ls -lrt' doesn't show the * as an executable, or a / as a directory. That is 'ls -F' .
 
Of course "xp1.txt*" will match xp1.txt followed by any character, including "*
 
Do you have write permission to the directories you're trying to move it from and to? Moving from and to a directory counts as modifying the directory, so you need write permissions to be able to do that.
 
ok, ignored.. hehe :)

vgersh99: gosh, U R right, I mean "star" not "start".. my original phrase sound quite stupid, doesn't it? hehe
 
If none of the above suggestions have helped, here's a different approach...
You might have problems with the "more" command instead of with that particular file. The "more" command (unlike "cat") tries to understand your TERM type and and display the file a page-at-a-time. On some OS's, it will complain if your TERM variable is unknown. Maybe on your OS, it fails silently.
Are you able to "cat" that file?
It could be that when you log in as "root", you are getting a different TERM value.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top