Re: [Jailkit-users] Jail broken after jk_init perl and jk_cp logger

[Dimitri]

On 10/12/20 8:10 pm, Olivier Sessink wrote:

On 10-12-2020 10:51, Dimitri wrote:

Thanks Olivier,  I will need to give some thought to (a) what I installed back then, and (b) how best to document it in a way that I can remember down the road. I never thought I would need to keep the jail updated separately from the base OS.  (In fact, the jail was created under U14 but I'm now running U16.  lol)

The only remaining issues I'm having at the moment, is that whilst the jail is working, (a) when I list directories ( ls -lha ) I see the uid & gid instead of username and groupname, and (b) the user's name in the prompt shows as "I have no name!".

I'm not sure what's causing this as both the global and local passwd and group files have the correct information and permissions.  I'm wondering if this is happening as a result of version conflicts that were caused as part of my addition of Perl to the jail.  I'm doing a DIFF between a working jail and this jail to see if I can spot anything.  Failing that, I might need to rerun jk_init on all the things I've place into the jail.

the library that supports this functionality is named 'libnss'. You can check if all libnss* files from your system are available in the jail.

Olivier

-- 
Bluefish website http://bluefish.openoffice.nl/
Blog http://oli4444.wordpress.com/

_______________________________________________
Jailkit-users mailing list
Jailkit-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/jailkit-users

Thanks again Olivier.  I actually was able to fix the problem via the advice you gave in your earlier response.  I used `jk_init` on all the modules I had setup previously.

The last anomaly I'm faced with now is that when I `chroot <rootJailFolder>`, I get a warning that the name for a group ID was not found.  The strange thing is that there are not files or folders in the jail that have that group ID, and it's not mentioned in either the local passwd or group files.  It is mentioned in the global versions, but there seems to be nothing wrong with the formatting.

To resolve the problem, I added a reference to that group in the local group file, which made the warning go away.  As this isn't really a solution, I'm now going investigate how to fix it properly.

Cheers, Dimitri.