Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!

Notices

Welcome to LinuxQuestions.org, a friendly and active Linux Community.

You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!

Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.

If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.

Having a problem logging in? Please visit this page to clear all LQ-related cookies.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

Yeah i have configured sudo and that does work but that's not really the reason i need it.

I am installing a piece of software that durring the install unpacks files and then attemps to change the owner of them and it is failing here.

Before you sugget it I am installing the software as root but durring the install it "su" to adminuser where adminuser is a user that will become the administrator for the new software. (Don't ask me why!)

So I have tried hacking the install script so that it uses "sudo chown ...." and gave adminuser access to sudo but that hasn't worked.

After some more debugging of the install script it turns out that the problem is not with the explicit "chown" commands although these would cause problems but it falls over before this on the following tar command.

The cd, gzip and tar commands you posted cannot change file ownership. They do however rely on file/directory access permissions. All they do is unzip/untar an existing file (/tmp/xxinstall/unpack/xxx/linux.tgz) into
a directory called /xxx/mydir.

If you want us to help you debug the script, please post (the relevant piece of) it.

Or alternative, try finding out why the commands you posted fail, starting off by posting the output of

Code:

ls -l /tmp/xxinstall/unpack/xxx
ls -ld /xxx/mydir/

Alternatively, you could also try adding 2>/tmp/error.log at the end of the pipe, to get a clue on what goes wrong.