superzebulon packages DO NOT create User in DSM.

[ramb0]

Hi,

Installed SABnzbd+ and SickBeard packages from superzebulon's resportory (http://synoblog.superzebulon.org/).

The "sabnzbd" and "sickbeard" users that are created, DO NOT show up in the DSM User's list.

Is this an error with the packages, or just the way it is?

[Ltek]

I don't know but the Sick Beard package work fine for me.

[ramb0]

I don't know but the Sick Beard package work fine for me.

When you go into your DSM and Control Panel > User > does sickbeard show up in your user list??

[avatar7]

I don't know but the Sick Beard package work fine for me.

When you go into your DSM and Control Panel > User > does sickbeard show up in your user list??

Not on mine it does not show. Should you manually add user as sickbeard?

[ramb0]

the Sick Beard package does add the user "sickbeard" to your Synology, how ever it just does not show up in the GUI of DSM... which brings me back to my original topic question...

[Goner]

I don't think it's an error with the packages .. it's just the way how users are created ; only users created in the Control Panel are show in DSM it seems.
You can see in /etc/passwd that the users are created in Linux, maybe there's a way to have them show up in DSM by placing them in a specific group or something ??

EDIT: it looks like DSM only controls the users with a User ID (UID) >= 1024 (which is admin)
I wonder if you can just change the UID in /etc/passwd ... any Linux gurus here ??

EDIT 2: looks like that's not a problem :
http://it.toolbox.com/blogs/locutus/how ... -gid-26368

[Ltek]

seems that ALL users should show up on the DM GUI... i they do not, this would be a bug IMO. Did anyone submit a bug ticket?

[Goner]

Nope ... I wouldn't even want all Linux users (especially those created by non-supported packages) in DSM. But if you think it's a bug, feel free

[rdgerken]

I noticed this too, but I think it might be specific to DSM 4. If I remember right, I DO remember seeing the users in the GUI prior to 4. (I had an alignment issue, so I reinstalled 4 from scratch, and noticed the users not showing up like you mentioned, but do not remember that back when I was on 3 something)

[rdgerken]

Goner,

Looks like you hit this one on the head. I wasn't able to get the usermod command to work, guess that's not built into the system, so I updated the passwd file manually, then ran "find / -user <old uid> -exec chown <new uid> {} \;" based off of the link you sent. Getting those UIDs up above 1024 or something does appear to make them show up in the GUI.

Any idea what the "passwd-" file is? Looks like it had a copy of the original UIDs when I started, but as I made the changes to the UIDs, those users disappeared from this file. I'm not sure if I should have updated that before running or not. Also, is running this "find" command necessary? Seems to take a long time to run on each user.

Thanks!

EDIT 1: For those of you struggling with this, if you try to follow what I did, I would recommend documenting the old UID and new UID you intend to assign for each user, make the change to the etc/passwd file (I don't know what to do with the passwd- file, I didn't do anything with it), reboot your diskstation, then for each user run the "find" command I specified above. When I tried running the find command without the reboot first, it threw some Operation not permitted errors. After the reboot, the find commands seemed to complete. I don't know if this is necessary, but most posts I found on the net made it sound like it was. I'm a total linux newb, so I really don't know if you want to trust what I'm doing or not. And then I did one final reboot to just make sure everything was in good order. After this process, my users now showed up in the GUI to where I could manage them.

[ramb0]

Goner,

Looks like you hit this one on the head. I wasn't able to get the usermod command to work, guess that's not built into the system, so I updated the passwd file manually, then ran "find / -user <old uid> -exec chown <new uid> {} \;" based off of the link you sent. Getting those UIDs up above 1024 or something does appear to make them show up in the GUI.

Any idea what the "passwd-" file is? Looks like it had a copy of the original UIDs when I started, but as I made the changes to the UIDs, those users disappeared from this file. I'm not sure if I should have updated that before running or not. Also, is running this "find" command necessary? Seems to take a long time to run on each user.

Thanks!

EDIT 1: For those of you struggling with this, if you try to follow what I did, I would recommend documenting the old UID and new UID you intend to assign for each user, make the change to the etc/passwd file (I don't know what to do with the passwd- file, I didn't do anything with it), reboot your diskstation, then for each user run the "find" command I specified above. When I tried running the find command without the reboot first, it threw some Operation not permitted errors. After the reboot, the find commands seemed to complete. I don't know if this is necessary, but most posts I found on the net made it sound like it was. I'm a total linux newb, so I really don't know if you want to trust what I'm doing or not. And then I did one final reboot to just make sure everything was in good order. After this process, my users now showed up in the GUI to where I could manage them.

Hey thanks for your input. this looks to be very useful. I think the find command you mention is definitely required as i think it's changing the file privileges of any user that you've changed the UID of.

I'm a total newb too, so i'm wondering if there are any other consequences to changing the passwd file manually and running the find command as you've mentioned.

seems odd that the DSM GUI only lists users with a UID of 1024 or greater. I guess there are other system users that are not needed to be seen in the DSM friendly GUI so they've made the GUI ignore any user with an UID < 1024.

Thanks again, this is great.