search

grover66 / kidtimer

Script to manage computer usage by time and schedule.
18 stars 23 forks source link

Can domain users be accounted for? #13

Closed ophbalance closed 10 years ago

ophbalance commented 10 years ago

Why is /etc/passwd queried when adding time for a user? The user files exist in the time folder, so I'm curious why addtime requires that a user be in the /etc/passwd file? I've got domain users set up, as I don't want to create a new local account for everyone in the house, and multiple machines running Ubuntu. Would it be possible to remove checking /etc/passwd for an existing user? Creating the schedule for the user went as expected, and it appears that things go awry after that step.

grover66 commented 10 years ago

Sure.

Will look at it in the next day or so.

Mike

On Wed, Apr 2, 2014 at 7:33 PM, ophbalance notifications@github.com wrote:

Why is /etc/passwd queried when adding time for a user? The user files exist in the time folder, so I'm curious why addtime requires that a user be in the /etc/passwd file? I've got domain users set up, as I don't want to create a new local account for everyone in the house, and multiple machines running Ubuntu. Would it be possible to remove checking /etc/passwd for an existing user? Creating the schedule for the user went as expected, and it appears that things go awry after that step.

Reply to this email directly or view it on GitHubhttps://github.com/grover66/kidtimer/issues/13 .

ophbalance commented 10 years ago

You know what? I think you can close this out. It's giving that error message but still correctly adds time to the .ttl file. I thought this was my issue, but ultimately I'm just an idiot and forgot I was pam mounting the schedule directory, where it needs to be an NFS mount. The cron to reset a users time was firing but there was nothing to act on in the schedule directory as there are no active users at that time of day.

grover66 commented 10 years ago

The issue I see you having is that since they are not local accounts, they cannot be locked via the "passwd -l " command. That would have to be kicked off on the AD server, not the Ubuntu clients.

I do not think it will work on non-local accounts.

Mike

On Thu, Apr 3, 2014 at 9:30 AM, ophbalance notifications@github.com wrote:

You know what? I think you can close this out. It's giving that error message but still correctly adds time to the .ttl file. I thought this was my issue, but ultimately I'm just an idiot and forgot I was pam mounting the schedule directory, where it needs to be an NFS mount. The cron to reset a users time was firing but there was nothing to act on in the schedule directory as there are no active users at that time of day.

Reply to this email directly or view it on GitHubhttps://github.com/grover66/kidtimer/issues/13#issuecomment-39450653 .

ophbalance commented 10 years ago

Well, they can get 5 minutes grace every time they log back in. That's just annoying enough that they won't attempt it for more than a few tries, so it works in a sense ;). There's not enough time to actually get involved with doing an activity so I'm fine with how that is. It was just my mistake for not mounting the schedules properly during boot instead of login.