Sir Tiger,

Try to check the sshd_config if the following parameter is set:

 AllowUsers    root

This will limit to only allow root access on the ssh service. config for sshd 
can be be found at /etc/ssh/sshd_config

maybe, it caused the problem you encountered.

K0l0s0s, COE

LPIC-1, NCLA, SCSA

Linux Registered User # 373129

Philippines

--- On Thu, 17/6/10, Bopolissimus Platypus Jr <[email protected]> 
wrote:

From: Bopolissimus Platypus Jr <[email protected]>
Subject: [plug] Cannot run processes as regular user
To: "Philippine Linux Users' Group (PLUG) Technical Discussion List" 
<[email protected]>
Received: Thursday, 17 June, 2010, 10:47 AM

Hi all,

I have a tonidoplug (ARM plugcomputer, running ubuntu jaunty) that
I've broken somehow.  I can ssh to it as root, but I can't ssh as a
regular user nor (once in as root) can I sudo, su or login as a
regular user.

I boot from a USB drive, so it's not a big deal, technically, to just
make another boot drive.  However the users will howl if I take it
offline to fix it :-).  Instead, I'm posting this as a puzzle that
interested people can try to help solve without rebooting :-).

1. Originally I had a good USB boot drive built as per tonido
instructions (first partition is /, optional swap second partition,
make first partition active and untar modules.tar.gz and rootfs.tar.gz
in the first partition).

2. I stopped the plugcomputer and brought that flash drive to another
computer, attached a laptop harddrive in USB enclosure (I wanted to
use the bigger drive as my new drive on the plugcomputer, there's only
one USB port, unfortunately).

3. I did a tgz of the flash drive and extracted that onto the first
partition of the laptop drive.

When I booted with the new drive all was well.

After installing a whole bunch of other packages though (I don't know
what all those packages are anymore, but just installing them should
not have broken jaunty this way) and miscellaneous fiddling, I found
out that I couldn't ssh as a regular user anymore, or (from root) sudo
as a regular user.

strace doesn't help much.  e.g., when I do:  "#strace -ff sudo su -u
tiger bash" at the end all I get is:

execve("/bin/bash", ["bash"], [/* 16 vars */] <unfinished ...>
+++ killed by SIGKILL +++

which I know, and which doesn't tell me why.

I'll certainly just install things again over the weekend.  But if I
can avoid the downtime and perhaps provide some entertainment to the
people on the list, all the better :-).

tiger

-- 
Gerald Timothy Quimpo http://bopolissimus.blogspot.com
[email protected] [email protected]

Even Tom Lane said: "Or, if you're worried
about actions from functions, use a trigger
to do the logging.  There are approximately
no cases where a rule is really better than
a trigger :-( "
_________________________________________________
Philippine Linux Users' Group (PLUG) Mailing List
http://lists.linux.org.ph/mailman/listinfo/plug
Searchable Archives: http://archives.free.net.ph



      
_________________________________________________
Philippine Linux Users' Group (PLUG) Mailing List
http://lists.linux.org.ph/mailman/listinfo/plug
Searchable Archives: http://archives.free.net.ph

Reply via email to