zoomzoom
Guru
- Joined
 - Sep 6, 2015
 
- Messages
 - 677
 
I changed the root home directory to the users directory I use for all all other users (/mnt/nas-system/users), as I store scripts and system files I've modified that need to be copied over after an update in the root home folder  (/root), which is not ideal due to /root being wiped after an update (I'm on nightlies).
The WebGUI requires the home directory to be on a dataset other than boot, also creating a problem is the boot dataset is not shown, ergo, once changed via the WebGUI, it's no longer possible to revert back to /root on the boot dataset for root's home directory.
	
		
			
		
		
	
			
			- I realized after changing the root home directory, all jails created now have the new directory (/mnt/nas-system/users/root) specified as their root home directory, which creates a major problem since ~ is now broken in all [non-plugin] jails created (not sure about plugin jails, as I don't use them).
 
Code:
[root@crashplan-1] /# cd ~ /mnt/nas-system/users/root: No such file or directory.
The WebGUI requires the home directory to be on a dataset other than boot, also creating a problem is the boot dataset is not shown, ergo, once changed via the WebGUI, it's no longer possible to revert back to /root on the boot dataset for root's home directory.
- While reverting root's home directory back to /root will save successfully in the WebGUI, it will remain unchanged after the save.
- Changing via 
chsh rootdoesn't work either. 
 - Changing via 
 - I also noticed when I went to edit root, and accidentally clicked on daemon instead, after selecting save I received the error "Home directory has to start with /mnt/ or be /nonexistent"
- Possible expected behavior as a safe guard against unintentional editing of system users?
 
 
			
				Last edited: