[ Date Index ]
[ Thread Index ]
[ <= Previous by date /
thread ]
[ Next by date /
thread => ]
Re: [LUG] Changing User ID.
- To: "list@xxxxxxxxxxxxx" <list@xxxxxxxxxxxxx>, Julian Hall <linux@xxxxxxxxxxxx>
- Subject: Re: [LUG] Changing User ID.
- From: mr meowski via list <list@xxxxxxxxxxxxx>
- Date: Mon, 10 Apr 2017 14:32:44 +0000
- Accept-language: en-GB, en-US
- Authentication-results: dcglug.org.uk; dkim=none (message not signed) header.d=none;dcglug.org.uk; dmarc=none action=none header.from=live.com;
- Content-id: <BF78743C179A5A44AF2AC97278EC5793@eurprd09.prod.outlook.com>
- Content-language: en-US
- Delivered-to: dclug@xxxxxxxxxxxxxxxxxxxxx
- Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=dclug.org.uk; s=1491642364; h=Sender:Content-Transfer-Encoding:Content-Type:Reply-To:From:List-Subscribe:List-Help:List-Post:List-Unsubscribe:List-Id:Subject:MIME-Version:Content-ID:In-Reply-To:References:Message-ID:Date:To; bh=wvNYNVPacWQsEEQtu1P48px1k+pjxCHQq0IKTB0ZYe8=; b=kkQiD6FmBQ/KccRwhnGUi1aTJGwTXTvQ2WkiHENdVdl0s5f1+4WGxIeF7bg6GdkXXi7+2TX977XGwJ0S2h6MRHMZrv0BjNBFHtu0IE6EsQUlJF9cpVAdyTEKAYySr92t03l6s8FrMQnYC25W8KYZgo74n264/1fWbtdUtoMnck8=;
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
- Thread-index: AQHSsS6o2o0tupp5VEKGoNz1XLHZRaG8+/GAgAGcR4CAABQFAA==
- Thread-topic: [LUG] Changing User ID.
On 10/04/17 14:20, Julian Hall via list wrote:
> Thanks Michael, unfortunately it didn't work as the laptop already has
> the same UID.
>
> Cerce ~ # id julian
> uid=1000(julian) gid=1000(julian)
> groups=1000(julian),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),113(lpadmin),130(sambashare)
>
> The output is the same on both machines. I'm at a loss now to understand
> why it thinks they are different users.
It would help to have the result of "ls -alh /path/to/problem/files" but
the short answer is to do:
chown -R $USER:$USER /path/to/problem/files
You might have fixed up your userid on the laptop to match now but the
files presumably have inherited some 'dodgy' permission bits, especially
if network storage was involved at some point (look out for the dreaded
'nfsuser' permissions for example), as was mentioned elsewhere.
You do have actually have +w on the files that are opening readonly right?
Cheers
--
The Mailing List for the Devon & Cornwall LUG
https://mailman.dclug.org.uk/listinfo/list
FAQ: http://www.dcglug.org.uk/listfaq
