[risolto] login da console

Tutto ciò che è pertinente a Sabayon Linux, indipendentemente dall'architettura e dall'ambiente grafico

Moderator: Moderators

Post Reply
marcb
Simple Hen
Posts: 86
Joined: Tue Jul 06, 2010 22:42

[risolto] login da console

Post by marcb » Wed Sep 12, 2018 9:42

dopo gli aggiornamenti delle ultime settimane, non riesco più ad effettuare il login da console, salvo che in modalità utente singolo.
non mi interessa abilitare questa funzione da remoto, ma in locale mi viene utile.
da cosa dipende? c'è un modo per ripristinare il comportamento precedente?
Last edited by marcb on Mon Oct 15, 2018 21:33, edited 1 time in total.

User avatar
sabayonino
Sagely Hen
Posts: 3279
Joined: Sun Sep 21, 2008 1:12
Location: Italy
Contact:

Re: login da console

Post by sabayonino » Wed Sep 12, 2018 10:50

Credo che dipenda da qualcosa relativo a PAM ma servono più info perchè potrebbe essere un problema slegato da quello che riscontro io

Io non riesco più ad editare il crontob utente

Code: Select all

LANG="en" crontab -e
You (myuser) are not allowed to access to (crontab) because of pam configuration.
Ovviamente il mio utente fa parte del gruppo crontab (ha sempre funzionato fin poco tempo fa) .

Appena ho più tempo vedo se riesco a segnalare la cosa.

[edit] Come non detto , ho reistallato sys-libs/pam-1.3.0-r2 ed è tornato tutto nella norma :mrgreen: :mrgreen:
[Che Cos'è Il Calcolo Distribuito (BOINC)

BOINC ready ! Sabayon+BOINC = BILD ,my Sabayon spin :cyclops: - Ready to crunch for the Science everywhere :)

marcb
Simple Hen
Posts: 86
Joined: Tue Jul 06, 2010 22:42

Re: login da console

Post by marcb » Thu Oct 11, 2018 7:54

ho provato a modificare questo file, ma senza successo :cry:

Code: Select all

/etc/security/access.conf

Code: Select all

# Disallow non-root logins on tty1
- : ALL EXCEPT root : tty1
# Allow non-root login on tty2 for emergencies
- : ALL EXCEPT myuser : tty2
# User root should be allowed to get access via cron .. tty1
+ : root : cron crond nobody :0 tty1
# Same for user myuser
+ : myuser : cron crond :0 tty1 tty2
# User myuser should get access from any address
+ : myuser : ALL
# Users root, myuser should be allowed to get access from loopback.
+ : root myuser : 127.0.0.1/32
# Users root, myuser should be denied to get access from all other sources.              
- : root myuser : ALL
# All other users should be denied to get access from all sources.
- : ALL : ALL

marcb
Simple Hen
Posts: 86
Joined: Tue Jul 06, 2010 22:42

Re: login da console

Post by marcb » Sun Oct 14, 2018 9:51

[edit] Come non detto , ho reistallato sys-libs/pam-1.3.0-r2 ed è tornato tutto nella norma :mrgreen: :mrgreen:
provato anche io ma senza successo :cry:

dopo aver annullato le modifiche del mio post precedente mi sono messo a guardare i log e ho visto che in realtà il login avviene, ma vengo subito disconnesso

ecco il log relativo ad un utente di prova che mi sono creato per partire da zero, il logout avviene immediatamente dopo il login

Code: Select all

Oct 14 10:42:27 sabayon systemd[1]: Started Getty on tty2.
Oct 14 10:42:34 sabayon login[4599]: pam_unix(login:session): session opened for user sabay by (uid=0)
Oct 14 10:42:34 sabayon systemd[1]: Created slice User Slice of sabay.
Oct 14 10:42:34 sabayon systemd[1]: Starting User Manager for UID 1001...
Oct 14 10:42:34 sabayon systemd-logind[1920]: New session 1 of user sabay.
Oct 14 10:42:34 sabayon systemd[4634]: pam_unix(systemd-user:session): session opened for user sabay by (uid=0)
Oct 14 10:42:34 sabayon systemd[1]: Started Session 1 of user sabay.
Oct 14 10:42:34 sabayon systemd[4634]: Reached target Timers.
Oct 14 10:42:34 sabayon systemd[4634]: Starting D-Bus User Message Bus Socket.
Oct 14 10:42:34 sabayon systemd[4634]: Reached target Paths.
Oct 14 10:42:34 sabayon systemd[4634]: Listening on D-Bus User Message Bus Socket.
Oct 14 10:42:34 sabayon systemd[4634]: Reached target Sockets.
Oct 14 10:42:34 sabayon systemd[4634]: Reached target Basic System.
Oct 14 10:42:34 sabayon systemd[4634]: Reached target Default.
Oct 14 10:42:34 sabayon systemd[4634]: Startup finished in 61ms.
Oct 14 10:42:34 sabayon systemd[1]: Started User Manager for UID 1001.
Oct 14 10:42:34 sabayon login[4599]: pam_unix(login:session): session closed for user sabay
Oct 14 10:42:34 sabayon systemd[1]: [email protected]: Service has no hold-off time, scheduling restart.
Oct 14 10:42:34 sabayon systemd[1]: Stopped Getty on tty2.
Oct 14 10:42:34 sabayon systemd[1]: Started Getty on tty2.
Oct 14 10:42:34 sabayon systemd-logind[1920]: Removed session 1.
Oct 14 10:42:34 sabayon systemd[1]: Stopping User Manager for UID 1001...
Oct 14 10:42:34 sabayon systemd[4634]: Stopped target Default.
Oct 14 10:42:34 sabayon systemd[4634]: Stopped target Basic System.
Oct 14 10:42:34 sabayon systemd[4634]: Stopped target Timers.
Oct 14 10:42:34 sabayon systemd[4634]: Stopped target Sockets.
Oct 14 10:42:34 sabayon systemd[4634]: Closed D-Bus User Message Bus Socket.
Oct 14 10:42:34 sabayon systemd[4634]: Stopped target Paths.
Oct 14 10:42:34 sabayon systemd[4634]: Reached target Shutdown.
Oct 14 10:42:34 sabayon systemd[4634]: Starting Exit the Session...
Oct 14 10:42:34 sabayon systemd[4634]: Received SIGRTMIN+24 from PID 4651 (kill).
Oct 14 10:42:34 sabayon systemd[4637]: pam_unix(systemd-user:session): session closed for user sabay
Oct 14 10:42:34 sabayon systemd[1]: Stopped User Manager for UID 1001.
Oct 14 10:42:34 sabayon systemd[1]: Removed slice User Slice of sabay.

marcb
Simple Hen
Posts: 86
Joined: Tue Jul 06, 2010 22:42

[risolto] login da console

Post by marcb » Mon Oct 15, 2018 21:35

scusate errore mio
avevo provato ad attivare la variabile

Code: Select all

export XDG_CACHE_HOME="/tmp/${USER}/.cache"
togliendo questa tutto funziona regolarmente, adesso vedro di capire meglio il problema

avevo preso il suggerimento da qui
Temporal files to tmpfs

marcb
Simple Hen
Posts: 86
Joined: Tue Jul 06, 2010 22:42

Re: [risolto] login da console

Post by marcb » Tue Oct 16, 2018 21:44

qui propongono un workaround al problema
XDG_CACHE_HOME & wrong kdm umask ?

Post Reply