Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #186931 > unrolled thread

making me automaticly logged in?

Back to article view | Back to linux.debian.user

Contents

  making me automaticly logged in? Gene Heskett <gheskett@shentel.net> - 2017-09-18 09:40 +0200
    Re: making me automaticly logged in? Darac Marjal <mailinglist@darac.org.uk> - 2017-09-18 11:20 +0200
      Re: making me automaticly logged in? Gene Heskett <gheskett@shentel.net> - 2017-09-18 17:20 +0200
        Re: making me automaticly logged in? Tixy <tixy@yxit.co.uk> - 2017-09-18 17:40 +0200
          Re: making me automaticly logged in? Gene Heskett <gheskett@shentel.net> - 2017-09-18 19:20 +0200
          Re: making me automaticly logged in? Gene Heskett <gheskett@shentel.net> - 2017-09-18 23:50 +0200
            Resetting USB devices (was Re: making me autocratically logged in?) Tixy <tixy@yxit.co.uk> - 2017-09-19 08:00 +0200
              Re: Resetting USB devices (was Re: making me autocratically logged in?) Gene Heskett <gheskett@shentel.net> - 2017-09-19 13:30 +0200

#186931 — making me automaticly logged in?

Greetings all;

I have one of my wheezy machines that has decided it shouldn't start any 
services until I have logged in on its own keyboard. I can't even ping 
it from the rest of my network now until I have logged in on its own 
keyboard.  It did not originally, and as recently as 2 months ago, it 
started everything and quietly waited showing the login dialog, while I 
was logged in with an ssh -Y session and doing anything I could from a 
terminal-4.8 console on this machine.

What does it take to automaticly log me in, so that the rest of the 
machine can function normally again. I am normally the only user on 
these machines. dd-wrt stands guard between my network and the cable 
modem, and has not been penetrated in 10+ years, so I am not concerned 
about the black hats crowd.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [next] | [standalone]

#186937

[Multipart message — attachments visible in raw view] — view raw

On Mon, Sep 18, 2017 at 03:35:04AM -0400, Gene Heskett wrote:
>Greetings all;
>
>I have one of my wheezy machines that has decided it shouldn't start any
>services until I have logged in on its own keyboard. I can't even ping
>it from the rest of my network now until I have logged in on its own
>keyboard.  It did not originally, and as recently as 2 months ago, it
>started everything and quietly waited showing the login dialog, while I
>was logged in with an ssh -Y session and doing anything I could from a
>terminal-4.8 console on this machine.
>
>What does it take to automaticly log me in, so that the rest of the
>machine can function normally again. I am normally the only user on
>these machines. dd-wrt stands guard between my network and the cable
>modem, and has not been penetrated in 10+ years, so I am not concerned
>about the black hats crowd.

That's a bit of a thorny issue. At the simplest, you could try 
installing something like nodm, which will start an X session for the 
configured user at boot.

If you're wanting automatic login at the console, then apparently you 
can pass the "-a $USER" (e.g. "-a bob" or "-a fred") argument to 
/sbin/getty. There's some more details on StackOverflow about that: 
<https://stackoverflow.com/questions/10282981/automatic-login-on-angstrom-linux#14148494>

However, I don't entirely know how these interact with PAM, or even with 
other services. So if some process is waiting for you to actually 
authenticate yourself (for example, cryptdisks or kerberos or anything 
security-based, I suppose), then these 'hacks' might not be sufficient, 
and you'd be better off finding out the root issue.

>
>Cheers, Gene Heskett
>-- 
>"There are four boxes to be used in defense of liberty:
> soap, ballot, jury, and ammo. Please use in that order."
>-Ed Howdershelt (Author)
>Genes Web page <http://geneslinuxbox.net:6309/gene>
>

-- 
For more information, please reread.

[toc] | [prev] | [next] | [standalone]

#186953

On Monday 18 September 2017 05:11:56 Darac Marjal wrote:

> On Mon, Sep 18, 2017 at 03:35:04AM -0400, Gene Heskett wrote:
> >Greetings all;
> >
> >I have one of my wheezy machines that has decided it shouldn't start
> > any services until I have logged in on its own keyboard. I can't
> > even ping it from the rest of my network now until I have logged in
> > on its own keyboard.  It did not originally, and as recently as 2
> > months ago, it started everything and quietly waited showing the
> > login dialog, while I was logged in with an ssh -Y session and doing
> > anything I could from a terminal-4.8 console on this machine.
> >
> >What does it take to automaticly log me in, so that the rest of the
> >machine can function normally again. I am normally the only user on
> >these machines. dd-wrt stands guard between my network and the cable
> >modem, and has not been penetrated in 10+ years, so I am not
> > concerned about the black hats crowd.
>
> That's a bit of a thorny issue. At the simplest, you could try
> installing something like nodm, which will start an X session for the
> configured user at boot.
>
> If you're wanting automatic login at the console, then apparently you
> can pass the "-a $USER" (e.g. "-a bob" or "-a fred") argument to
> /sbin/getty. There's some more details on StackOverflow about that:
> <https://stackoverflow.com/questions/10282981/automatic-login-on-angst
>rom-linux#14148494>
>
> However, I don't entirely know how these interact with PAM, or even
> with other services. So if some process is waiting for you to actually
> authenticate yourself (for example, cryptdisks or kerberos or anything
> security-based, I suppose), then these 'hacks' might not be
> sufficient, and you'd be better off finding out the root issue.
>
That machine is running the TDE desktop, like this one is as it has 
enough resources to do it nicely. All the rest of them are running LXDE, 
or XFDE as the case may be. And they have not been afflicted with this. 

However, it appears there isn't a live mailing listserver at 
lists.pearsoncomputing.net, 3 posts in the last 48 hours have not been 
echo'd although I can ping the machine by its FQDN just fine.  IRC 
channel has low activity but seems to be working, however I think I'm 
the only biped logged in with uncovered eyeballs ATM.

My instant problem, a disappearing usb camera, could also be solved I 
think, by power cycling the usb port its plugged into, as it will 
re-appear after a powerdown reboot, but I do not know how to do that 
short of a powerdown reset.  If there is such an ability the user, or a 
sudo can do, that would also be helpfull.

> >Cheers, Gene Heskett
> >--
> >"There are four boxes to be used in defense of liberty:
> > soap, ballot, jury, and ammo. Please use in that order."
> >-Ed Howdershelt (Author)
> >Genes Web page <http://geneslinuxbox.net:6309/gene>


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#186955

On Mon, 2017-09-18 at 11:13 -0400, Gene Heskett wrote:
[...]
> My instant problem, a disappearing usb camera, could also be solved I 
> think, by power cycling the usb port its plugged into, as it will 
> re-appear after a powerdown reboot, but I do not know how to do that 
> short of a powerdown reset.  If there is such an ability the user, or a 
> sudo can do, that would also be helpfull.

I don't know if this is useful, but the method I found for resetting a
USB device was to unbind then rebind it with something like:

echo '3-1.4' >/sys/bus/usb/drivers/usb/unbind
echo '3-1.4' >/sys/bus/usb/drivers/usb/bind

Where '3-1.4' is the endpoint name for the device found by looking in
the kernel log. E.g. for this example I ran the 'dmesg' command and
looked for my web camera and found these entries:

usb 3-1.4: new high-speed USB device number 3 using ehci-pci
usb 3-1.4: New USB device found, idVendor=2232, idProduct=1018
usb 3-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 3-1.4: Product: WebCam SC-13HDL11431N

I don't know if this will help with your particular problem.

-- 
Tixy

[toc] | [prev] | [next] | [standalone]

#186959

On Monday 18 September 2017 11:39:26 Tixy wrote:

> On Mon, 2017-09-18 at 11:13 -0400, Gene Heskett wrote:
> [...]
>
> > My instant problem, a disappearing usb camera, could also be solved
> > I think, by power cycling the usb port its plugged into, as it will
> > re-appear after a powerdown reboot, but I do not know how to do that
> > short of a powerdown reset.  If there is such an ability the user,
> > or a sudo can do, that would also be helpfull.
>
> I don't know if this is useful, but the method I found for resetting a
> USB device was to unbind then rebind it with something like:
>
> echo '3-1.4' >/sys/bus/usb/drivers/usb/unbind
> echo '3-1.4' >/sys/bus/usb/drivers/usb/bind
>
> Where '3-1.4' is the endpoint name for the device found by looking in
> the kernel log. E.g. for this example I ran the 'dmesg' command and
> looked for my web camera and found these entries:
>
> usb 3-1.4: new high-speed USB device number 3 using ehci-pci
> usb 3-1.4: New USB device found, idVendor=2232, idProduct=1018
> usb 3-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
> usb 3-1.4: Product: WebCam SC-13HDL11431N
>
> I don't know if this will help with your particular problem.
Looks ideal, but the hub/port.number does't exist. I'll go reboot it and 
see what it shows up that tree.  Back in a bit.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#186976

On Monday 18 September 2017 11:39:26 Tixy wrote:

> On Mon, 2017-09-18 at 11:13 -0400, Gene Heskett wrote:
> [...]
>
> > My instant problem, a disappearing usb camera, could also be solved
> > I think, by power cycling the usb port its plugged into, as it will
> > re-appear after a powerdown reboot, but I do not know how to do that
> > short of a powerdown reset.  If there is such an ability the user,
> > or a sudo can do, that would also be helpfull.
>
> I don't know if this is useful, but the method I found for resetting a
> USB device was to unbind then rebind it with something like:
>
> echo '3-1.4' >/sys/bus/usb/drivers/usb/unbind
> echo '3-1.4' >/sys/bus/usb/drivers/usb/bind
>
> Where '3-1.4' is the endpoint name for the device found by looking in
> the kernel log. E.g. for this example I ran the 'dmesg' command and
> looked for my web camera and found these entries:
>
> usb 3-1.4: new high-speed USB device number 3 using ehci-pci
> usb 3-1.4: New USB device found, idVendor=2232, idProduct=1018
> usb 3-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
> usb 3-1.4: Product: WebCam SC-13HDL11431N
>
> I don't know if this will help with your particular problem.

Wheezy apparently isn't organized in quite that manner. So the best I 
could do, even as root, was elicit no permissions messages.

Going out to the machine, I found a middle of the night power failure had 
rebooted it, but this time the networking was working normally while it 
was waiting for me to login.

Firing up linuxcnc, the camera was there, but the video went away as I 
was expanding the size of the linuxcnc window.  Stop and restart 
linuxcnc, and it works until I expand the window vertically enough to 
start seeing the video chains controls.  Shut down and go get a 
different camera & plug it in, works, but frame rate is only about 7 fps 
and the colors are off some, its a much older endoscope  camera.  Start 
to expand the window enough to start seeing the controls, and that 
camera stops delivering video.  Restart LCNC again, but click on the 
full screen icon, works, back to small window, works. I switch it 
several times, works everytime, back to small window and drag it to 
upper left of screen, dies.  But now neither has gone away in the lsusb 
list.

There ought to be an excedrin headache number, but I'm also the head cook 
around here.  Wife has broken hip, so I'm doing it all.

Thanks for reading. If you've an idea, I'll be back after dinner.



Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#186990 — Resetting USB devices (was Re: making me autocratically logged in?)

On Mon, 2017-09-18 at 17:49 -0400, Gene Heskett wrote:
> On Monday 18 September 2017 11:39:26 Tixy wrote:
> 
> > On Mon, 2017-09-18 at 11:13 -0400, Gene Heskett wrote:
> > [...]
> >
> > > My instant problem, a disappearing usb camera, could also be solved
> > > I think, by power cycling the usb port its plugged into, as it will
> > > re-appear after a powerdown reboot, but I do not know how to do that
> > > short of a powerdown reset.  If there is such an ability the user,
> > > or a sudo can do, that would also be helpfull.
> >
> > I don't know if this is useful, but the method I found for resetting a
> > USB device was to unbind then rebind it with something like:
> >
> > echo '3-1.4' >/sys/bus/usb/drivers/usb/unbind
> > echo '3-1.4' >/sys/bus/usb/drivers/usb/bind
> >
> > Where '3-1.4' is the endpoint name for the device found by looking in
> > the kernel log. E.g. for this example I ran the 'dmesg' command and
> > looked for my web camera and found these entries:
> >
> > usb 3-1.4: new high-speed USB device number 3 using ehci-pci
> > usb 3-1.4: New USB device found, idVendor=2232, idProduct=1018
> > usb 3-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
> > usb 3-1.4: Product: WebCam SC-13HDL11431N
> >
> > I don't know if this will help with your particular problem.
> 
> Wheezy apparently isn't organized in quite that manner. So the best I 
> could do, even as root, was elicit no permissions messages.

Strange, I'm using Jessie, but looks like unbinding has been supported
in the kernel for over 10 years [1] so would expect a Wheezy kernel to
support it, perhaps the path is different. Does a file at that path
exist? For me I get 

#ls -l /sys/bus/usb/drivers/usb/unbind
--w------- 1 root root 4096 Sep 19 06:28 /sys/bus/usb/drivers/usb/unbind

Actually, looking at that old article [1] the path is different
(/sys/bus/usb/drivers/ub/) so perhaps you might try that, or any other
likely path you may have under /sys/bus/usb/drivers/

BTW, I'm sure you realised this, but to make it explicit, the magic
string '3-1.4' in my example is specific to my machine and yours will be
different depending on the USB hub/device topography.

I have no experience with webcam problems so can't help with that
specificly. (I use this USB driver unbind/bind trick to get an FTDI
development module to toggle it's power enable output)

[1] https://lwn.net/Articles/143397/

-- 
Tixy

[toc] | [prev] | [next] | [standalone]

#186997 — Re: Resetting USB devices (was Re: making me autocratically logged in?)

On Tuesday 19 September 2017 01:53:25 Tixy wrote:

> On Mon, 2017-09-18 at 17:49 -0400, Gene Heskett wrote:
> > On Monday 18 September 2017 11:39:26 Tixy wrote:
> > > On Mon, 2017-09-18 at 11:13 -0400, Gene Heskett wrote:
> > > [...]
> > >
> > > > My instant problem, a disappearing usb camera, could also be
> > > > solved I think, by power cycling the usb port its plugged into,
> > > > as it will re-appear after a powerdown reboot, but I do not know
> > > > how to do that short of a powerdown reset.  If there is such an
> > > > ability the user, or a sudo can do, that would also be helpfull.
> > >
> > > I don't know if this is useful, but the method I found for
> > > resetting a USB device was to unbind then rebind it with something
> > > like:
> > >
> > > echo '3-1.4' >/sys/bus/usb/drivers/usb/unbind
> > > echo '3-1.4' >/sys/bus/usb/drivers/usb/bind
> > >
> > > Where '3-1.4' is the endpoint name for the device found by looking
> > > in the kernel log. E.g. for this example I ran the 'dmesg' command
> > > and looked for my web camera and found these entries:
> > >
> > > usb 3-1.4: new high-speed USB device number 3 using ehci-pci
> > > usb 3-1.4: New USB device found, idVendor=2232, idProduct=1018
> > > usb 3-1.4: New USB device strings: Mfr=1, Product=2,
> > > SerialNumber=0 usb 3-1.4: Product: WebCam SC-13HDL11431N
> > >
> > > I don't know if this will help with your particular problem.
> >
> > Wheezy apparently isn't organized in quite that manner. So the best
> > I could do, even as root, was elicit no permissions messages.
>
> Strange, I'm using Jessie, but looks like unbinding has been supported
> in the kernel for over 10 years [1] so would expect a Wheezy kernel to
> support it, perhaps the path is different. Does a file at that path
> exist? For me I get
>
> #ls -l /sys/bus/usb/drivers/usb/unbind
> --w------- 1 root root 4096 Sep 19 06:28
> /sys/bus/usb/drivers/usb/unbind
>
> Actually, looking at that old article [1] the path is different
> (/sys/bus/usb/drivers/ub/) so perhaps you might try that, or any other
> likely path you may have under /sys/bus/usb/drivers/
>
> BTW, I'm sure you realised this, but to make it explicit, the magic
> string '3-1.4' in my example is specific to my machine and yours will
> be different depending on the USB hub/device topography.
>
> I have no experience with webcam problems so can't help with that
> specificly. (I use this USB driver unbind/bind trick to get an FTDI
> development module to toggle it's power enable output)
>
> [1] https://lwn.net/Articles/143397/

Its there, when the camera is, but all that is cleared out when the 
camera has disappeared.

I have found it will reappear if unplugged, then plugged back in.  But it 
probably will go away again. Along with all the stuff in its /sys path.

I went out to the shop and retrieved an older camera which isn't near as 
fast or as accurate color. This one hasn't disappeared, yet, but the app 
can be full screened and back to 1/4 screen by the size switch.  But the 
video stream will die just like the other camera if I try to manually 
adjust the apps window size.

So I have 2 problems. I may as well get another camera, but the ebay 
people don't consider close focusing to be important or useful, and the 
author needs to look at the code too.  Or playing mix and match between 
pyvcp and gladevcp is being a problem. Each has its own capability's, or 
lacks a needed capability.

In any event, I now know enough that I know I am asking the wrong list.

My thanks to all who tried to help.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web