This is very strange. When I boot up my box and login as a user I can use
screen. But if I booted up and logged in as root first and then su user, the
user have the error message displayed in the subject line. Any ideas?
--
German
On 13 March 2015 15:52:41 GMT+00:00, German wrote:
> This is very strange. When I boot up my box and login as a user I can
> use screen. But if I booted up and logged in as root first and then su
> user, the user have the error message displayed in the subject line.
> Any ideas?
>
> --
> German
On Fri, 13 Mar 2015 15:59:04 +
Neil Bothwick wrote:
> On 13 March 2015 15:52:41 GMT+00:00, German wrote:
> > This is very strange. When I boot up my box and login as a user I can
> > use screen. But if I booted up and logged in as root first and then su
> > user, the user have the error mess
On Fri, Mar 13, 2015 at 10:06 AM, German wrote:
>
> On Fri, 13 Mar 2015 15:59:04 +
> Neil Bothwick wrote:
>
> > On 13 March 2015 15:52:41 GMT+00:00, German
wrote:
> > > This is very strange. When I boot up my box and login as a user I can
> > > use screen. But if I booted up and logged in as
On Fri, 13 Mar 2015 10:11:58 -0600
Canek Peláez Valdés wrote:
> On Fri, Mar 13, 2015 at 10:06 AM, German wrote:
> >
> > On Fri, 13 Mar 2015 15:59:04 +
> > Neil Bothwick wrote:
> >
> > > On 13 March 2015 15:52:41 GMT+00:00, German
> wrote:
> > > > This is very strange. When I boot up my box
On Fri, Mar 13, 2015 at 10:22 AM, German wrote:
[ ... ]
> > Are you using logind?
>
> Good question. What is logind? How I can find out what am I using?
If you are using systemd, you are using logind. Otherwise you are not.
Regards.
--
Canek Peláez Valdés
Profesor de asignatura, Facultad de Cien
On Fri, 13 Mar 2015 10:31:11 -0600
Canek Peláez Valdés wrote:
> On Fri, Mar 13, 2015 at 10:22 AM, German wrote:
> [ ... ]
> > > Are you using logind?
> >
> > Good question. What is logind? How I can find out what am I using?
>
> If you are using systemd, you are using logind. Otherwise you are
On Fri, 13 Mar 2015 15:59:04 +
Neil Bothwick wrote:
> On 13 March 2015 15:52:41 GMT+00:00, German wrote:
> > This is very strange. When I boot up my box and login as a user I can
> > use screen. But if I booted up and logged in as root first and then su
> > user, the user have the error mess
On Fri, 13 Mar 2015 15:16:28 -0400, German wrote:
> after searching, I found the following solution to chmod tty1, like so:
> chmod o+rw /dev/tty1 and this worked, I was able to use screen as a
> user, however it doesn't stay permanently; after reboot, I got the same
> problem. How to chmod tty1 s
Neil Bothwick wrote:
> On Fri, 13 Mar 2015 15:16:28 -0400, German wrote:
>
> > after searching, I found the following solution to chmod tty1, like
> > so: chmod o+rw /dev/tty1 and this worked, I was able to use screen
> > as a user, however it doesn't stay permanently; after reboot, I got
> > th
On Friday 13 March 2015 22:28:29 Neil Bothwick wrote:
> A Smith & Weason beats Four Aces everytime.
A Smith and what?
--
Rgds
Peter.
On Sat, 14 Mar 2015 00:00:34 +0100
wrote:
> Neil Bothwick wrote:
>
> > On Fri, 13 Mar 2015 15:16:28 -0400, German wrote:
> >
> > > after searching, I found the following solution to chmod tty1, like
> > > so: chmod o+rw /dev/tty1 and this worked, I was able to use screen
> > > as a user, howev
On Sat, 14 Mar 2015 00:00:34 +0100, waben...@gmail.com wrote:
> > /dev/tty1 is already group writeable, so you should get the same
> > result by adding your user to the tty group.
>
> When I logged in as regular user then ownership of the tty that I
> used for log in is:
>
> crw--- 1 wabe
On Fri, 13 Mar 2015 23:10:22 +, Peter Humphrey wrote:
> On Friday 13 March 2015 22:28:29 Neil Bothwick wrote:
> > A Smith & Weason beats Four Aces everytime.
>
> A Smith and what?
You have far too much time on your hands!
I only steal taglines, I don't spell-check them.
--
Neil Bothwic
On Fri, 13 Mar 2015 23:22:50 +, Neil Bothwick wrote:
> Interesting, here, as a normal user:
>
> % ls -l /dev/tty1
> crw--w 1 root tty 4, 1 Mar 13 22:26 /dev/tty1
>
> > So it seems that after login you first have to chmod 770 the tty
> > before you do a su - user (user have to be in group
On Fri, 13 Mar 2015 23:28:32 +
Neil Bothwick wrote:
> On Fri, 13 Mar 2015 23:22:50 +, Neil Bothwick wrote:
>
> > Interesting, here, as a normal user:
> >
> > % ls -l /dev/tty1
> > crw--w 1 root tty 4, 1 Mar 13 22:26 /dev/tty1
> >
> > > So it seems that after login you first have to
On Friday 13 March 2015 23:25:21 Neil Bothwick wrote:
> On Fri, 13 Mar 2015 23:10:22 +, Peter Humphrey wrote:
> > On Friday 13 March 2015 22:28:29 Neil Bothwick wrote:
> > > A Smith & Weason beats Four Aces everytime.
> >
> > A Smith and what?
>
> You have far too much time on your hands!
Tr
On Friday 13 March 2015 23:28:32 Neil Bothwick wrote:
> I have this in /lib/udev/rules.d/50-udev-default.rules:
>
> SUBSYSTEM=="tty", KERNEL=="tty[0-9]*", GROUP="tty", MODE="0620"
# grep tty /lib/udev/rules.d/50-udev-default.rules
SUBSYSTEM=="tty", KERNEL=="ptmx", GROUP="tty", MODE="0666"
SUBSYS
Peter Humphrey wrote:
> On Friday 13 March 2015 23:28:32 Neil Bothwick wrote:
>
> > I have this in /lib/udev/rules.d/50-udev-default.rules:
> >
> > SUBSYSTEM=="tty", KERNEL=="tty[0-9]*", GROUP="tty", MODE="0620"
>
> # grep tty /lib/udev/rules.d/50-udev-default.rules
> SUBSYSTEM=="tty", KERNEL=
wrote:
> Peter Humphrey wrote:
>
> > On Friday 13 March 2015 23:28:32 Neil Bothwick wrote:
> >
> > > I have this in /lib/udev/rules.d/50-udev-default.rules:
> > >
> > > SUBSYSTEM=="tty", KERNEL=="tty[0-9]*", GROUP="tty", MODE="0620"
> >
> > # grep tty /lib/udev/rules.d/50-udev-default.rules
wrote:
> Neil Bothwick wrote:
>
> > On Fri, 13 Mar 2015 15:16:28 -0400, German wrote:
> >
> > > after searching, I found the following solution to chmod tty1,
> > > like so: chmod o+rw /dev/tty1 and this worked, I was able to use
> > > screen as a user, however it doesn't stay permanently; aft
On Sat, 14 Mar 2015 01:16:32 +0100
wrote:
> wrote:
>
> > Neil Bothwick wrote:
> >
> > > On Fri, 13 Mar 2015 15:16:28 -0400, German wrote:
> > >
> > > > after searching, I found the following solution to chmod tty1,
> > > > like so: chmod o+rw /dev/tty1 and this worked, I was able to use
> >
On Sat, 14 Mar 2015 06:08:34 -0400, German wrote:
> > Forget about "chmod 770". Better do a "chmod g+rw". :-)
>
> Tried it, it also doesn't stay permanently. OK, no solution :(
The correct solution is a udev rule, but it appears that something may be
overriding that when you login. A kludgy so
On Sat, 14 Mar 2015 10:33:59 +
Neil Bothwick wrote:
> On Sat, 14 Mar 2015 06:08:34 -0400, German wrote:
>
> > > Forget about "chmod 770". Better do a "chmod g+rw". :-)
> >
> > Tried it, it also doesn't stay permanently. OK, no solution :(
>
> The correct solution is a udev rule, but it a
On Fri, Mar 13, 2015 at 8:14 PM, wrote:
> wrote:
>> Peter Humphrey wrote:
>>> On Friday 13 March 2015 23:28:32 Neil Bothwick wrote:
I have this in /lib/udev/rules.d/50-udev-default.rules:
SUBSYSTEM=="tty", KERNEL=="tty[0-9]*", GROUP="tty", MODE="0620"
>>>
>>> # grep tty /lib
On Sat, Mar 14, 2015 at 6:08 AM, German wrote:
> On Sat, 14 Mar 2015 01:16:32 +0100 wrote:
>> wrote:
>>>
>>> So it seems that after login you first have to chmod 770 the tty
>>> before you do a su - user (user have to be in group tty of course).
>>
>> Forget about "chmod 770". Better do a "chmod
> On Mar 14, 2015, at 12:47, German wrote:
>
> On Sat, 14 Mar 2015 10:33:59 +
> Neil Bothwick wrote:
>
>> On Sat, 14 Mar 2015 06:08:34 -0400, German wrote:
>>
Forget about "chmod 770". Better do a "chmod g+rw". :-)
>>>
>>> Tried it, it also doesn't stay permanently. OK, no solution
On 14/03/2015 20:53, Matti Nykyri wrote:
>> On Mar 14, 2015, at 12:47, German wrote:
>>
>> On Sat, 14 Mar 2015 10:33:59 +
>> Neil Bothwick wrote:
>>
>>> On Sat, 14 Mar 2015 06:08:34 -0400, German wrote:
>>>
> Forget about "chmod 770". Better do a "chmod g+rw". :-)
Tried it, it
> On Mar 14, 2015, at 21:23, Alan McKinnon wrote:
>
> There is a use-case for doing it (but I highly doubt the OP is using it)
Yes. I was just thinking if the OP has a miss configuration in
/etc/security/access.conf and can't login as himself on a local console. And
that way is forced to use r
On Saturday 14 March 2015 20:53:44 Matti Nykyri wrote:
> Don't hit your head to a brick wall. A small strace to the login
> process reveals that login set things as you tell it to in
> /etc/login.defs
>
> In this file change the line:
> TTYPERM 0600
> To:
> TTYPERM 0620
>
> And your problem is f
On Sat, 14 Mar 2015 10:33:59 +
Neil Bothwick wrote:
> On Sat, 14 Mar 2015 06:08:34 -0400, German wrote:
>
> > > Forget about "chmod 770". Better do a "chmod g+rw". :-)
> >
> > Tried it, it also doesn't stay permanently. OK, no solution :(
>
> The correct solution is a udev rule, but it a
On Sat, 14 Mar 2015 14:03:21 -0400
Tom H wrote:
> On Sat, Mar 14, 2015 at 6:08 AM, German wrote:
> > On Sat, 14 Mar 2015 01:16:32 +0100 wrote:
> >> wrote:
> >>>
> >>> So it seems that after login you first have to chmod 770 the tty
> >>> before you do a su - user (user have to be in group tty
On Sat, 14 Mar 2015 20:53:44 +0200
Matti Nykyri wrote:
> > On Mar 14, 2015, at 12:47, German wrote:
> >
> > On Sat, 14 Mar 2015 10:33:59 +
> > Neil Bothwick wrote:
> >
> >> On Sat, 14 Mar 2015 06:08:34 -0400, German wrote:
> >>
> Forget about "chmod 770". Better do a "chmod g+rw". :
> On Mar 17, 2015, at 18:11, German wrote:
>
>> Don't hit your head to a brick wall. A small strace to the login process
>> reveals that login set things as you tell it to in /etc/login.defs
>>
>> In this file change the line:
>> TTYPERM 0600
>> To:
>> TTYPERM 0620
>>
>> And your problem is fi
On Tue, 17 Mar 2015 19:16:42 +0200
Matti Nykyri wrote:
> > On Mar 17, 2015, at 18:11, German wrote:
> >
> >> Don't hit your head to a brick wall. A small strace to the login process
> >> reveals that login set things as you tell it to in /etc/login.defs
> >>
> >> In this file change the line:
> On Mar 17, 2015, at 19:33, German wrote:
>
> On Tue, 17 Mar 2015 19:16:42 +0200
> Matti Nykyri wrote:
>
On Mar 17, 2015, at 18:11, German wrote:
Don't hit your head to a brick wall. A small strace to the login process
reveals that login set things as you tell it to in /
On Tue, 17 Mar 2015 20:39:46 +0200
Matti Nykyri wrote:
> > On Mar 17, 2015, at 19:33, German wrote:
> >
> > On Tue, 17 Mar 2015 19:16:42 +0200
> > Matti Nykyri wrote:
> >
> On Mar 17, 2015, at 18:11, German wrote:
>
> Don't hit your head to a brick wall. A small strace to the
> On Mar 17, 2015, at 21:52, German wrote:
>
> On Tue, 17 Mar 2015 20:39:46 +0200
> Matti Nykyri wrote:
>
>>> On Mar 17, 2015, at 19:33, German wrote:
>>>
>>> On Tue, 17 Mar 2015 19:16:42 +0200
>>> Matti Nykyri wrote:
>>>
>> On Mar 17, 2015, at 18:11, German wrote:
>>
>> Don't
On Tue, 17 Mar 2015 22:14:03 +0200
Matti Nykyri wrote:
> > On Mar 17, 2015, at 21:52, German wrote:
> >
> > On Tue, 17 Mar 2015 20:39:46 +0200
> > Matti Nykyri wrote:
> >
> >>> On Mar 17, 2015, at 19:33, German wrote:
> >>>
> >>> On Tue, 17 Mar 2015 19:16:42 +0200
> >>> Matti Nykyri wrote:
On Tue, Mar 17, 2015 at 11:42 AM, German wrote:
> On Sat, 14 Mar 2015 14:03:21 -0400, Tom H wrote:
>>
>> Canek had asked whether you were using systemd and therefore logind.
>> Since you're using openrc, perhaps you should check whether installing
>> consolekit is a fix because it's the precursor
On Fri, 13 Mar 2015 15:59:04 +
Neil Bothwick wrote:
> On 13 March 2015 15:52:41 GMT+00:00, German wrote:
> > This is very strange. When I boot up my box and login as a user I can
> > use screen. But if I booted up and logged in as root first and then su
> > user, the user have the error mess
41 matches
Mail list logo
