similar to: lastlog oddity

This is.... odd. We're seeing a *lot* of sshd[8400]: Timeout, client not responding. So I'm trying to find out whose client is having issues. Trying to figure that, after processes are gone, I tried looking in lastlog, which is where it gets odd. lastlog shows root coming in, and it shows a security account coming in... years ago. I see one of our users logging in a goodly number of

Hi, Can any of you explain this weirdness: [root at machine log]# cd /var/log/ [root at machine log]# ls -la|grep last -r-------- 1 root root 1254130450140 Nov 6 21:44 lastlog [root at machine log]# du -hs lastlog 52K lastlog What's up with the output of ls? This is x86_64. Thanks, Morten

Hi, just built 2.3.0p1 on HP-UX 10.20 more or less smoothly >From 1.2.3 I had documented --without-lastlog, can't remember why, broke something. So I tried my old configure settings for 2.3.0 which seams to break stuff: loginrec.c:1338: warning: `struct lastlog' declared inside parameter list some more dereferencing pointers and then Error 1 [of course] Omitting the

Hi list, this problem is already known and I'm sorry to bother if an acceptable workaround was already debated on the list. I was getting trouble with a 'grep something /var/log*' which caused the "Memory exhausted" message. With some deeper search I found the lastlog file in /var/log/ to be 1.2T sized. This seems to come from the nfsnobody's uid to be 4294967294 on

Hi, I just ltraced ssh to see why it prints the lastlog twice instead of one time. I think the bug seems to be in the parsing of the lastlog-entry and I especially think that the function lastlog_populate_entry is the buggy one, but I'm not sure, as I'm not very familar with the code. So if someone of you, would please trace this bug down and fix it, I would really appreciate that.

Somewhere between 2.9p1 and 2.9.9p2 there was a change to auth2.c that removed the userauth_reply() function. There were a few lines of code in that function, #ifdef'd with WITH_AIXAUTHENTICATE, that handled the AIX method of lastlog type stuff (specifically, a loginsuccess() call). There is a similar call in auth1.c, down in do_authentication(), which is still there in 2.9.9p2. So with

i haven't heard of problems with configure/lastlog on 10.20. i'll copy the development list as there are folks there who use 10.20. On Thu, 6 Sep 2001, Jesse Caldwell wrote: :one last problem with openssh -- building openssh on HPUX 10.20 fails :on loginrec.c (i don't have the errors handy but i would be more than :happy to recreate them). i get the same error with 2.9p2 and 9/6/2001

Marcelo Roccasalva wrote: > On Tue, Jan 30, 2018 at 3:26 PM, <m.roth at 5-cent.us> wrote: >> >> This is.... odd. >> >> We're seeing a *lot* of >> sshd[8400]: Timeout, client not responding. > > Is it possible you are testing ssh availability from nagios, monit, or > some other software that connects to the port 22 without logging in? > Ok, I

On 2015-04-08, Leon Fauster <leonfauster at googlemail.com> wrote: > Am 08.04.2015 um 16:22 schrieb Liam O'Toole > <liam.p.otoole at gmail.com>: >> On 2015-04-08, David Both >> <dboth at millennium-technology.com> >> wrote: >>> The easy way to restart gdm is when you are on the login screen >>> itself or the desktop simply press

https://bugzilla.mindrot.org/show_bug.cgi?id=2278 Bug ID: 2278 Summary: 'configure --disable-lastlog' should mark PrintLastLog as unsupported in servconf.c Product: Portable OpenSSH Version: 6.6p1 Hardware: All OS: Solaris Status: NEW Severity: minor Priority: P5

Folks; I couldn't find anything on my archive of the mailing list on this, and it may just be my mis-understanding, but: When I "ssh machine1 -l user1" as user2 on machine2, if user2 has the same uid on machine1, then user2's name ends up in lastlog, instead of user1's. This is a bit disconcerting when user2 is root, and root isn't allowed to remotely log in on

https://bugzilla.mindrot.org/show_bug.cgi?id=1774 Summary: wtmp and lastlog on AIX Product: Portable OpenSSH Version: 5.5p1 Platform: All OS/Version: AIX Status: NEW Severity: normal Priority: P2 Component: Build system AssignedTo: unassigned-bugs at mindrot.org ReportedBy: defrayable at

On 2015-04-08, David Both <dboth at millennium-technology.com> wrote: > The easy way to restart gdm is when you are on the login screen itself > or the desktop simply press Ctrl-Alt-Backspace. This works for Upstart > in CentOS 6.x but will not work for CentOS 7.x which uses Systemd. The > service command does not work for gdm. However, logging out of the > desktop will

On 2015-04-04, Bill Maltby (C4B) <centos4bill at gmail.com> wrote: > On Sat, 2015-04-04 at 11:12 +0100, Nux! wrote: >> 100% with Digimer here. <snip> > >> All this energy should be put into contributing towards to the >> project, testing, helping out community. > > Well, I used to agree. But when a bug report filed in December goes > untouched entering

yum upgrade -y yada yada yada .... then lots of errors like: /usr/share/gnome/help/gdm/fr/gdm.xml:173: parser error : Entity 'eacute' not defined and so on until Document is not well-formed XML: /usr/share/gnome/help/gdm/it/gdm.xml Updating : amtu ##################### [173/520] Updating : grub ##################### [174/520] ...

Gordon Messmer wrote: > On 12/15/2015 11:26 AM, m.roth at 5-cent.us wrote: >> Really? There's no systemd target to restart it, and graphical.target >> doesn't do it? Um..... > > Why do you think that? Sorry, I would have thought that graphical.target would do it. And suppose I'm using kdm...? mark > > # systemctl status gdm.service > gdm.service -

grep face /home/<username> -r :) -- David Fix Senior Systems Administrator Mr. X Inc. ----- Original Message ----- From: "m roth" <m.roth at 5-cent.us> To: "CentOS mailing list" <centos at centos.org> Sent: Friday, September 18, 2009 9:01:27 AM Subject: Re: [CentOS] gdm-simple-greeter config? > Greetings, > > On Fri, Sep 18, 2009 at

Liam O'Toole wrote: > On 2015-04-09, Ole Holm Nielsen > <Ole.H.Nielsen at fysik.dtu.dk> wrote: >> After we upgraded our CentOS 7.0 desktops to CentOS 7.1, a critical >> error in the graphical login screen has appeared on all 7.1 machines: >> >> We have 100+ users defined in /etc/passwd, and a list of names is >> presented on the initial login screen.

Paul Heinlein wrote: > On Tue, 17 May 2016, m.roth at 5-cent.us wrote: > >> I'm hoping *someone* here has worked a bit with bareos. I've tried >> posting to the google groups for it... and haven't even had one person >> view my post.... >> >> It was working fine, backing up windows boxes for months. Then, about >> a week ago, the server got

Hi while testing a new pam module i found this problem: System: Linux 2.4.18/OpenSSH 3.8p1 client/server The output from do_login() in session.c (motd, lastlog, stored pam messages) isn't displayed when Privilege Separation is enabled. I added a fflush(stdout) as the last line of do_login(), now it works. Frank