Autologon Desktop on Ubuntu 18.04 after exchange of disk that is mounted on /home












0















I've got a Server running on that some user has got an low rights user that ist automated doing its login, so the users are able to use all the allowed functions.



Now the drive has got problems and one part at the end is broken. It is one of the big files that are not more needed and it is a raid that is there broken.



So I get all the data on a new drive and I did copy all with copying any user itself to the new substitution drive. The copy did not tell any faults and I thought everything is fine but when I do now change the entries in fstab, so that this drive is mounted on /home , I am able do login with password as another operator is able but the automated lowlevel user is not more starting automated and I could even watch, that after login in the user gets kickt out very soon after a short while and I have no idea what is wrong in this case.



Is there anything that I should know about or that I must preserv for this or change?



I did copy the data wich cp -a /home/user /newhome/ and the copy seems proper after I did remove the file that is in the area on the broken part of this drives. But I do want to change the drives out after it and don't want to develop all new for the main users with low level, as I don't want to train them all a new thing.



If I mount the nehhome with fstab on /home it isn't working proper but I am able to login with my own account and the major operator as well only the automated one low level User isn't logged in automated and gets kicked out after a short while.



I do really not know what I've made wrong.










share|improve this question























  • Did you make sure that all the hidden directories and files (those startingwith a dot) was copied too ?

    – Soren A
    Feb 2 at 16:51











  • That was my first thought. But why should than my own user work, where the settings are as well in files starting with a dot. two of 3 users work proper and it is only the user that is been automated logged on that doesn't works. I did try inbetween now shopt -s dotglob ; cp -a /home/user /newhome/ will check the wrights soon. but need to call in the system for that.

    – Andreas Bartels
    Feb 2 at 19:07
















0















I've got a Server running on that some user has got an low rights user that ist automated doing its login, so the users are able to use all the allowed functions.



Now the drive has got problems and one part at the end is broken. It is one of the big files that are not more needed and it is a raid that is there broken.



So I get all the data on a new drive and I did copy all with copying any user itself to the new substitution drive. The copy did not tell any faults and I thought everything is fine but when I do now change the entries in fstab, so that this drive is mounted on /home , I am able do login with password as another operator is able but the automated lowlevel user is not more starting automated and I could even watch, that after login in the user gets kickt out very soon after a short while and I have no idea what is wrong in this case.



Is there anything that I should know about or that I must preserv for this or change?



I did copy the data wich cp -a /home/user /newhome/ and the copy seems proper after I did remove the file that is in the area on the broken part of this drives. But I do want to change the drives out after it and don't want to develop all new for the main users with low level, as I don't want to train them all a new thing.



If I mount the nehhome with fstab on /home it isn't working proper but I am able to login with my own account and the major operator as well only the automated one low level User isn't logged in automated and gets kicked out after a short while.



I do really not know what I've made wrong.










share|improve this question























  • Did you make sure that all the hidden directories and files (those startingwith a dot) was copied too ?

    – Soren A
    Feb 2 at 16:51











  • That was my first thought. But why should than my own user work, where the settings are as well in files starting with a dot. two of 3 users work proper and it is only the user that is been automated logged on that doesn't works. I did try inbetween now shopt -s dotglob ; cp -a /home/user /newhome/ will check the wrights soon. but need to call in the system for that.

    – Andreas Bartels
    Feb 2 at 19:07














0












0








0








I've got a Server running on that some user has got an low rights user that ist automated doing its login, so the users are able to use all the allowed functions.



Now the drive has got problems and one part at the end is broken. It is one of the big files that are not more needed and it is a raid that is there broken.



So I get all the data on a new drive and I did copy all with copying any user itself to the new substitution drive. The copy did not tell any faults and I thought everything is fine but when I do now change the entries in fstab, so that this drive is mounted on /home , I am able do login with password as another operator is able but the automated lowlevel user is not more starting automated and I could even watch, that after login in the user gets kickt out very soon after a short while and I have no idea what is wrong in this case.



Is there anything that I should know about or that I must preserv for this or change?



I did copy the data wich cp -a /home/user /newhome/ and the copy seems proper after I did remove the file that is in the area on the broken part of this drives. But I do want to change the drives out after it and don't want to develop all new for the main users with low level, as I don't want to train them all a new thing.



If I mount the nehhome with fstab on /home it isn't working proper but I am able to login with my own account and the major operator as well only the automated one low level User isn't logged in automated and gets kicked out after a short while.



I do really not know what I've made wrong.










share|improve this question














I've got a Server running on that some user has got an low rights user that ist automated doing its login, so the users are able to use all the allowed functions.



Now the drive has got problems and one part at the end is broken. It is one of the big files that are not more needed and it is a raid that is there broken.



So I get all the data on a new drive and I did copy all with copying any user itself to the new substitution drive. The copy did not tell any faults and I thought everything is fine but when I do now change the entries in fstab, so that this drive is mounted on /home , I am able do login with password as another operator is able but the automated lowlevel user is not more starting automated and I could even watch, that after login in the user gets kickt out very soon after a short while and I have no idea what is wrong in this case.



Is there anything that I should know about or that I must preserv for this or change?



I did copy the data wich cp -a /home/user /newhome/ and the copy seems proper after I did remove the file that is in the area on the broken part of this drives. But I do want to change the drives out after it and don't want to develop all new for the main users with low level, as I don't want to train them all a new thing.



If I mount the nehhome with fstab on /home it isn't working proper but I am able to login with my own account and the major operator as well only the automated one low level User isn't logged in automated and gets kicked out after a short while.



I do really not know what I've made wrong.







server permissions mount login fstab






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Feb 2 at 16:31









Andreas BartelsAndreas Bartels

32




32













  • Did you make sure that all the hidden directories and files (those startingwith a dot) was copied too ?

    – Soren A
    Feb 2 at 16:51











  • That was my first thought. But why should than my own user work, where the settings are as well in files starting with a dot. two of 3 users work proper and it is only the user that is been automated logged on that doesn't works. I did try inbetween now shopt -s dotglob ; cp -a /home/user /newhome/ will check the wrights soon. but need to call in the system for that.

    – Andreas Bartels
    Feb 2 at 19:07



















  • Did you make sure that all the hidden directories and files (those startingwith a dot) was copied too ?

    – Soren A
    Feb 2 at 16:51











  • That was my first thought. But why should than my own user work, where the settings are as well in files starting with a dot. two of 3 users work proper and it is only the user that is been automated logged on that doesn't works. I did try inbetween now shopt -s dotglob ; cp -a /home/user /newhome/ will check the wrights soon. but need to call in the system for that.

    – Andreas Bartels
    Feb 2 at 19:07

















Did you make sure that all the hidden directories and files (those startingwith a dot) was copied too ?

– Soren A
Feb 2 at 16:51





Did you make sure that all the hidden directories and files (those startingwith a dot) was copied too ?

– Soren A
Feb 2 at 16:51













That was my first thought. But why should than my own user work, where the settings are as well in files starting with a dot. two of 3 users work proper and it is only the user that is been automated logged on that doesn't works. I did try inbetween now shopt -s dotglob ; cp -a /home/user /newhome/ will check the wrights soon. but need to call in the system for that.

– Andreas Bartels
Feb 2 at 19:07





That was my first thought. But why should than my own user work, where the settings are as well in files starting with a dot. two of 3 users work proper and it is only the user that is been automated logged on that doesn't works. I did try inbetween now shopt -s dotglob ; cp -a /home/user /newhome/ will check the wrights soon. but need to call in the system for that.

– Andreas Bartels
Feb 2 at 19:07










1 Answer
1






active

oldest

votes


















0














It may be an ownership problem, try fixing it with the following commands.



Changing ownership of the home where username is your "lowlevel" account:



sudo chown username:username /newhome


Tell the system the home for the account has changed:



sudo usermod -m -d /newhome username


Also give the right permissions to the home:



sudo chmod 755 /newhome





share|improve this answer
























  • Thanks for asking that again the last was it. I don't know when the mod of home changed to 555 and I am not able to understand why a cp -a isn't preserving all. But now it works.

    – Andreas Bartels
    Feb 3 at 19:13











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1115029%2fautologon-desktop-on-ubuntu-18-04-after-exchange-of-disk-that-is-mounted-on-hom%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














It may be an ownership problem, try fixing it with the following commands.



Changing ownership of the home where username is your "lowlevel" account:



sudo chown username:username /newhome


Tell the system the home for the account has changed:



sudo usermod -m -d /newhome username


Also give the right permissions to the home:



sudo chmod 755 /newhome





share|improve this answer
























  • Thanks for asking that again the last was it. I don't know when the mod of home changed to 555 and I am not able to understand why a cp -a isn't preserving all. But now it works.

    – Andreas Bartels
    Feb 3 at 19:13
















0














It may be an ownership problem, try fixing it with the following commands.



Changing ownership of the home where username is your "lowlevel" account:



sudo chown username:username /newhome


Tell the system the home for the account has changed:



sudo usermod -m -d /newhome username


Also give the right permissions to the home:



sudo chmod 755 /newhome





share|improve this answer
























  • Thanks for asking that again the last was it. I don't know when the mod of home changed to 555 and I am not able to understand why a cp -a isn't preserving all. But now it works.

    – Andreas Bartels
    Feb 3 at 19:13














0












0








0







It may be an ownership problem, try fixing it with the following commands.



Changing ownership of the home where username is your "lowlevel" account:



sudo chown username:username /newhome


Tell the system the home for the account has changed:



sudo usermod -m -d /newhome username


Also give the right permissions to the home:



sudo chmod 755 /newhome





share|improve this answer













It may be an ownership problem, try fixing it with the following commands.



Changing ownership of the home where username is your "lowlevel" account:



sudo chown username:username /newhome


Tell the system the home for the account has changed:



sudo usermod -m -d /newhome username


Also give the right permissions to the home:



sudo chmod 755 /newhome






share|improve this answer












share|improve this answer



share|improve this answer










answered Feb 2 at 16:46









Cristian VrinceanuCristian Vrinceanu

1025




1025













  • Thanks for asking that again the last was it. I don't know when the mod of home changed to 555 and I am not able to understand why a cp -a isn't preserving all. But now it works.

    – Andreas Bartels
    Feb 3 at 19:13



















  • Thanks for asking that again the last was it. I don't know when the mod of home changed to 555 and I am not able to understand why a cp -a isn't preserving all. But now it works.

    – Andreas Bartels
    Feb 3 at 19:13

















Thanks for asking that again the last was it. I don't know when the mod of home changed to 555 and I am not able to understand why a cp -a isn't preserving all. But now it works.

– Andreas Bartels
Feb 3 at 19:13





Thanks for asking that again the last was it. I don't know when the mod of home changed to 555 and I am not able to understand why a cp -a isn't preserving all. But now it works.

– Andreas Bartels
Feb 3 at 19:13


















draft saved

draft discarded




















































Thanks for contributing an answer to Ask Ubuntu!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1115029%2fautologon-desktop-on-ubuntu-18-04-after-exchange-of-disk-that-is-mounted-on-hom%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Mouse cursor on multiple screens with different PPI

Agildo Ribeiro

Sometime when accessing a menu: “Ubuntu 16.04 has experienced an internal error”