VectorLinux
October 30, 2014, 03:56:33 am *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Visit our home page for VL info. To search the old message board go to http://vectorlinux.com/forum1. The first VL forum is temporarily offline until we can find a host for it. Thanks for your patience.
 
Now powered by KnowledgeDex.
   Home   Help Search Login Register  
Please support VectorLinux!
Pages: [1]
  Print  
Author Topic: How to restrict daily user session time in VL 6.0?  (Read 1871 times)
Sta1ker
Member
*
Posts: 8


« on: February 15, 2011, 01:16:57 pm »

Hi,

I've just got VL Light 6.0 installed on old laptop for my kid.
Now the task is - restrict daily user session time. I other distributions like Ubuntu I've used timeoutd that doesn't look compiled for VL.

I've tried to convert and install existing rpm package with no luck. Then I compiled this daemon from sources.

Now I cannot find any guide how to add the new service to VL having daemon compiled.

Could anybody suggest any place or give some idea how to do so. I hope compiled daemon will work under VL.

Thank you.
Logged
rm-r
DoucheBag
Vectorite
***
Posts: 115


« Reply #1 on: February 15, 2011, 02:13:47 pm »

Disclaimer - Never having used this function am on shaky grounds here -

However, this seems about correct:

http://www.fir3net.com/General-UNIX/bash-korn-change-the-default-session-timeout.html

Please note the difference to global file   bashrc  vs user's local  (dot) bashrc
The first is always parsed at bootup , the second is  applied per individual  user when logged in

AFAIK,  to test, creat a (dot) .bashrc file,  then  use
#source .bashrc

HTH
Logged

"Problems are seldom resolved by thinking in the same manner they were created"

"What is viewed is not important - That which is seen is"
newt
Vectorian
****
Posts: 1132



« Reply #2 on: February 15, 2011, 02:27:10 pm »

One potential obstacle is a missing dependency: debhelper (>= 4)

As a quick test I grabbed the source and patch. Patched the source. Compiled (make) the source. Attempted to start the daemon 'timeoutd' but it did not appear in my process list, but did not provide any error/closing message either. Tried running the daemon several times and never did it appear in my process list. I'm not certain what the problem is here but it may be a dependency issue - YMMV.

The package may be too tied into the debian/ubuntu architecture to be used on a slackware-based OS, but this is just speculation. Maybe there's a similar daemon already in existence for slack-based distros that just needs to be discovered. If I happen across such a system timer daemon I'll be certain to post a link here.
Logged
rm-r
DoucheBag
Vectorite
***
Posts: 115


« Reply #3 on: February 15, 2011, 02:44:43 pm »

Pure guessing here,  but try man timeout ( a bash command)  then see man pages

BTW - did you use ldd on the source_or view any log files when attempting to run
Logged

"Problems are seldom resolved by thinking in the same manner they were created"

"What is viewed is not important - That which is seen is"
newt
Vectorian
****
Posts: 1132



« Reply #4 on: February 15, 2011, 02:59:49 pm »

No, I did not use ldd on source nor did I look too deeply into the log files. It was a quick-and-dirty test.

I did give another method a shot and had better success. I downloaded the debian deb package; converted to tar.gz package using 'deb2targz'; renamed to .tgz package; installed using 'installpkg name_of_package.tgz'; edited the /etc/timeouts config file to disallow a specific user from logging in; ran the daemon; and tested the user that was disallowed. Everything mostly works. The package gets installed and is immediately usable.  The daemon runs and stays running. I then tested the disallowed user and they are able to login but after about 5-10 seconds they get a message indicating that logins are not allowed at this time and they are dumped back to the login screen. Overall, fairly successful - I'm not going to get much done in 5-10 second intervals, especially if it involves the internet.

HTH.
Logged
rm-r
DoucheBag
Vectorite
***
Posts: 115


« Reply #5 on: February 15, 2011, 03:49:27 pm »

Heh,  no arguing w/success - good work   !

(Personally,  I don't get much done BECAUSE of  internet > hrs & hrs of research  finding info
then  forgetting &/or  trying "creative" duhhs.)


Logged

"Problems are seldom resolved by thinking in the same manner they were created"

"What is viewed is not important - That which is seen is"
rm-r
DoucheBag
Vectorite
***
Posts: 115


« Reply #6 on: February 16, 2011, 10:06:35 am »

Stalker

LOL -

In our zeal to apply computer  technology to your  request -
It overlooks a basic trouble-shooting princilple
Find the simplist solution by re-examining the intent

I.E. - Do you really  want to  delegate parental control to A.I.

Isn't the whole idea to teach the child to abide by "house rules" ?
Personally I would explain the  limitations - (and why)  - if that gets ignored,
use a cheap. LOUD timer to "tattle"  on them     

(Be aware - kids are quick learners,  very inventive ~ next thing you know your
inquisitive "child" may  re-program the computer to limit  *your* access) 
 
Remember the slogan - So simple a 5yr can do it"
Adult - "where's a - xxxx  when I need one "
Logged

"Problems are seldom resolved by thinking in the same manner they were created"

"What is viewed is not important - That which is seen is"
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!