Sponsored Content
Operating Systems Linux Locked out of Mandrake 9.1 user account Post 52800 by Tux on Saturday 26th of June 2004 12:38:30 PM
Old 06-26-2004
Are you trying to log is as root?

I'm not sure in which version they introduced it, but at some point Mandrake changed their default settings so that root could not log into the GUI.
Have a look through your settings in mcc.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How to Enable locked root account

Hi Every one I disable the root account entering wrong password for many time How can I enable the root account I am using Tru64 Unix V4.0G Thank you (2 Replies)
Discussion started by: Syed_45
2 Replies

2. AIX

root account has been locked

I'am set the root account locked ON, using smitty, so I can't login or su with root user in my AIX system, some one can help me to unlock root account login ???, sample : :~>su root's Password: 3004-301 Your account has been locked; please see the system administrator. 3004-501 Cannot su to... (1 Reply)
Discussion started by: Maker
1 Replies

3. HP-UX

Re-enabling a locked root account on Trusted HP-UX

I knew I had had seen this somewhere:Q: How can I re-enable my root account when I typed in my password wrong 3 times and the account got disabled? A: When your HP-UX system is in the more secure "trusted system" mode, your account is automatically disabled after you have entered your password... (0 Replies)
Discussion started by: Perderabo
0 Replies

4. AIX

account is always locked out

we have a user name "Test1" that account is alwyas locked out. The user has been used to many servers to ftp a file from the main server. i already increase the MaxStartups to 99. And still after how many days account will locked. (3 Replies)
Discussion started by: invinzin21
3 Replies

5. UNIX for Dummies Questions & Answers

Difference between : Locked User Account & Disabled User Accounts in Linux ?

Thanks AVKlinux (3 Replies)
Discussion started by: avklinux
3 Replies

6. Solaris

Banner for Locked Account

Hi, I have enable Account lock for failed login attempts. I have configured 1) /etc/security/policy.conf 2)/etc/default/login To lock an account if it make multiple incorrect attempts to login to Solaris 10 server. I can see the account gets locked in /etc/shadow. I would like to... (1 Reply)
Discussion started by: menonk
1 Replies

7. UNIX for Dummies Questions & Answers

How do i list all locked account in linux?

Hi How do i list all locked account in my linux distributiion I have tried passwd -S -a but it seems to not working . My distribution details. # lsb_release -a LSB Version: :core-3.1-ia32:core-3.1-noarch:graphics-3.1-ia32:graphics-3.1-noarch Distributor ID: OracleVMserver... (3 Replies)
Discussion started by: pinga123
3 Replies

8. UNIX for Dummies Questions & Answers

Account is locked or login administratively denied

Hi, When I am trying to do ssh to a server it shows below error. Key setup is all good and it used to work well few days back. Now suddenly I am getting this error. ssh -i <private_key> <id>@<hostname> Received disconnect from <hostname> Account is locked or login administratively... (1 Reply)
Discussion started by: mahish20
1 Replies

9. Solaris

Particular user account shouldn't be locked after entering wrong passwd specfic no. times

Hi all In my system we have implemented user lockout feature after 3 failure attempt if he tries to login directly or if he run the any command through sudo and enter wrong password thrice. Now I have requirement in which particular user account shouldn't be locked when he run the command... (1 Reply)
Discussion started by: sb200
1 Replies

10. Solaris

User account get locked due to strange behaviours

I am facing strange problem where after three failed login attempt user password must be locked. Actually what is happening, when I take the putty session of the server & enter user name on the prompt at the login prompt & then press enter to enter the password at this time when I checked the... (10 Replies)
Discussion started by: sb200
10 Replies
LR_VENDOR_CRON.IN(1)					  LogReport's Lire Documentation				      LR_VENDOR_CRON.IN(1)

NAME
lr_vendor_cron - generate Lire reports from all known log files on the system SYNOPSIS
lr_vendor_cron daily|weekly|monthly DESCRIPTION
lr_vendor_cron is designed to be invoked by cron. On systems supporting /etc/cron.d/, this script can be invoked by creating /etc/cron.d/lire, which should read e.g.: 02 5 * * * root /usr/sbin/lr_vendor_cron daily 22 5 * * 0 root /usr/sbin/lr_vendor_cron weekly 42 5 1 * * root /usr/sbin/lr_vendor_cron monthly lr_vendor_cron reads files /etc/sysconfig/lire.d/*.cfg and /etc/default/lire.d/*.cfg. For each log file, such a file should exist. The files should set the following shell variables: daemon the name of a binary which generated the specific log. This is used to test wether the *.cfg-file is suitable for the current system. If you'd like to generate a log for which no daemon is present on the current system, just use a placeholder like "daemon=/bin/true". service a Lire service, e.g. sendmail, logfile e.g. /var/log/mail.log.1.gz, filter e.g. 'gzip -dc' or 'zcat | grep sendmail', and rotateperiod one of the supported lr_vendor_cron arguments. extraopts optional: extra options passed to lr_log2mail(1). Set this to e.g. '--template www_local'. After parsing the configuration files, lr_vendor_cron invokes lr_log2mail(1) on the `filter'ed log file. Reading and filtering the log is done as root, lr_log2mail is run as user lire, using su(1). Output is fed to logger(1). SECURITY
lr_vendor_cron is supposed to be run as root. However, please note that this script is distributed WITHOUT ANY WARRANTY. If you don't like to run such a script as root, make sure your lire user has read access to all log files you'd like to get processed, and adapt this script. We supply this script mainly for people building packages. On many Unix and GNU/Linux distributions, it's hard to enforce log file readability by the lire user. This script is mainly a way to work around this. ENVIRONMENT VARIABLES
lr_vendor_cron honours DEBUG, CONFDIR, PRIORITY (for logger(1) call), and LIREUSER. Beware! PRIORITY as used here is independent of the LR_FACILITY as set in /etc/lire/defaults. This script does not use any of the settings in /etc/lire/defaults. VERSION
$Id: lr_vendor_cron.in,v 1.14 2006/07/23 13:16:33 vanbaal Exp $ COPYRIGHT
Copyright (C) 2002, 2003 Stichting LogReport Foundation LogReport@LogReport.org Copyright (C) 2005 Joost van Baal This program is part of Lire. Lire is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program (see COPYING); if not, check with http://www.gnu.org/copyleft/gpl.html. AUTHORS
Francis J. Lacoste <flacoste@logreport.org>, Joost van Baal <joostvb@logreport.org> Lire 2.1.1 2006-07-23 LR_VENDOR_CRON.IN(1)
All times are GMT -4. The time now is 06:41 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy