[-_-] | Hi | 00:31 |
---|---|---|
[-_-] | https://paste.debian.net/plain/1292409 | 00:32 |
[-_-] | and this is the error : https://paste.debian.net/plain/1292410 | 00:32 |
[-_-] | that is /etc/pam.d/common-session | 00:33 |
[-_-] | also I can't figure out who is using common-session, a grep through / don't show any script using that file | 00:34 |
[-_-] | So it is not clear to me how to add anything to pam | 00:34 |
Necrodiver | gnarface: nah, my friend had to go to sleep so we just put it off for a few days since he cant physically bring the pc over here for me to check it out | 00:35 |
Necrodiver | i was looking into other possible reasons, and one of them was going into the bios. He has never owned a pc of any kind of his own before, asking him to go into the bios would be REAL bad lol | 00:36 |
gnarface | [-_-]: "@include common-session" shows up in almost a dozen other files in /etc/pam.d/ for me. | 00:37 |
[-_-] | yeah, but I am trying to get an understanding of pam | 00:37 |
[-_-] | say I wanna execute a script with pam as I did there, where would I add the entry? | 00:38 |
[-_-] | why? | 00:38 |
[-_-] | does order matter in pam ? | 00:38 |
[-_-] | pam manpage is not fully clear to me | 00:38 |
gnarface | [-_-]: what'd you do? delete all the stock ones and replace them with gentoo ones then wonder why it stopped working? the files it shows up in for me mostly are directly named after the programs that use them. | 00:39 |
[-_-] | no, I did not, only modified that file | 00:39 |
gnarface | [-_-]: how did the other entries not show up for you in grep then? | 00:39 |
[-_-] | I can still remove that line and there are no errors | 00:40 |
[-_-] | they did, I wanted to find the source where any of the pam files were being called / used, I tried login and common-session | 00:40 |
[-_-] | noone seems to use those | 00:40 |
[-_-] | I did not try su or su-l | 00:40 |
gnarface | [-_-]: aiui, programs built with pam support find their own file name in /etc/pam.d/ and read it directly to figure out how to behave. there's no init scripts involved in the process. i recall an old bug where changes to /etc/pam.d/ won't be recognized until you update the timestamps on all the files in the directory though... | 00:46 |
[-_-] | :o | 00:47 |
[-_-] | meaning all of them have to have same date and time? | 00:47 |
gnarface | [-_-]: i think it just mattered that they were all of a later date than the build date of some pam package or something. not sure... if you're not doing this locally though, but rather through a remote ssh shell, maybe you're just editing the wrong file though, since in that case you'd actually want to be editing the ssh one | 00:48 |
[-_-] | I am doing this locally | 00:49 |
[-_-] | time for timestamp editing I think | 00:49 |
gnarface | just touch all the files, and the directory itself, then reboot for good measure, see if it behaves any better | 00:50 |
[-_-] | alr | 00:50 |
[-_-] | guys, I have found the problem | 01:39 |
[-_-] | the script pam_exec calls, has to be executable :D | 01:39 |
[-_-] | but what does exit status 13 mean, I could not get it on internet | 01:40 |
[-_-] | this just appeared to me, tried, and suddenly there were no errors | 01:41 |
gnarface | heh, well, clearly status 13 means the script didn't work | 01:42 |
gnarface | well, i found status codes here, not sure if they're the ones you're looking for though: https://pubs.opengroup.org/onlinepubs/8329799/chap5.htm | 01:43 |
gnarface | [PAM_USER_UNKNOWN] 13 The user is not known to the underlying account management module. | 01:44 |
gnarface | maybe those are internal to the API, though. i don't know if they count for shell return codes too. | 01:45 |
gnarface | hmm, maybe "man pam_strerror" will help something you're doing? | 01:46 |
gnarface | i think you're in over my head here, but i just discovered there's a whole bunch of pam related man pages, and some of them appear to have actual C API notes in them | 01:47 |
[-_-] | it is ok now | 01:47 |
gnarface | the pam_exec man page might be a good starting point if you haven't seen it | 01:47 |
[-_-] | I have | 01:47 |
[-_-] | it has return values defined as constant, but not the numerical constant that we need | 01:48 |
[-_-] | ummmmm....I think I would call them arbitrary constants | 01:48 |
gnarface | "man pam_strerror" describes a function to get the error string from one of those constants | 01:49 |
gnarface | but it seems like you'd have to write C code to use it | 01:49 |
gnarface | i note also though there's a pam(3) and pam(7) man page both | 01:49 |
gnarface | some of the other ones might also have buddies | 01:50 |
[-_-] | anyway, the errors in pam_exec manpage are not very specific | 01:53 |
gnarface | well you got it working, so i suppose that's the important part | 01:55 |
[-_-] | :D | 01:56 |
[-_-] | btw gnarface & DPA: thanks guys | 02:10 |
gnarface | np | 02:11 |
[-_-] | :) | 02:15 |
nethead23 | Hello, any tips on where to find info on how to install php-fpm on Devuan 5 / Daedalus? | 11:28 |
DelTomix | nethead23: Generally it should be exactly the same as with Debian - what version are you trying to set up? | 12:03 |
DPA | [-_-]: Error 13 isn't a pam error but a C / POSIX errno value. To see what number means what, the errno utility from moreutils can be very handy. The command `errno 13` will tell you that it means "EACCES 13 Permission denied", which makes sense when the execute permission on the script was missing. "errno -l" gives a list of all the error codes. | 12:24 |
DPA | Oh, seams he has already left... | 12:28 |
gnarface | good info though, DPA | 12:46 |
gnarface | nethead23: it appears to be present, are you having an issue with it? | 12:47 |
russnes | I initiated installing kde-plasma-desktop with apt, but I saw that it listed systemd as an optional package. Does this mean that it will install systemd along with kde? I'm running a fresh daedalus install with xfce made from from the desktop-live | 13:34 |
rrq | for me it mentions "systemd-coredump" as a recommends but I don't think that's available in the repo. Do you get something else than that? | 13:49 |
dave_p | After the latest upgrade to the distro, my display will no longer run or allow me to select or run my display at 1920x1080 @ 60.00 Hz. I'm using Xfce (standard install). Any suggestions? | 14:44 |
dave_p | Those settings are what I am using right now since I booted off the old kernel. | 14:45 |
micdud | debootstraping excalibur (cron-daemon-common depends on systemd | systemd-standalone-sysusers | systemd-sysusers; however:......not installed etc.....) | 14:58 |
psionic | What time is the new Ashoka Today | 20:59 |
psionic | ? | 20:59 |
gnarface | if dave_p comes back, ask them if they're using nvidia drivers. they may need to install build deps and re-run dkms | 21:40 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!