09-02-2010
Depends how they were "locked out". If it's just file permissions, you should be able to access anything as root. They may also be on a totally different partition. If it's anything else, you'll have to tell us what's going on, we can't see your computer from here.
Last edited by Corona688; 09-02-2010 at 05:56 PM..
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have some locked files ( locked via the Mac finder)
I have tired rm -R and rm -rdf but it doesnt delete the locked files
just says "override rw------- etc?"
type "yes" and says "operation not permitted"
is there some way to do this (or unlock the files)
Thanks (1 Reply)
Discussion started by: Aussie John
1 Replies
2. AIX
good morning
just a confirmation, to lock a password for a user, we must to write 0 for password min age and password max age option ?
thank you (0 Replies)
Discussion started by: pascalbout
0 Replies
3. HP-UX
:confused:
I have an K580 HP server.
All I did was change the IP address on the NIC and now I can't telnet into it.
I can ping, but no telnet.
Also, it won't boot if the console monitor is plugged in.
ANY IDEAS??? (1 Reply)
Discussion started by: ncmurf00
1 Replies
4. AIX
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
using OS X and the Terminal, I'd like to find all locked files in a specified directory, unlock them, and print a list of those files that were unlocked
how can I do this?
I'm familiar with chflags nouchg for unlocking one file but not familiar with unix enough to do what I'd like.
Thanks! (0 Replies)
Discussion started by: alternapop
0 Replies
6. UNIX for Advanced & Expert Users
I am running Solaris 10. Occasionally, my id gets loked. I want to know who/which rougue process locked it.
How do I find out?
Thanks,
KNK (9 Replies)
Discussion started by: nkamatam
9 Replies
7. AIX
How to can find all locked files and release the locks in Unix?
We have an issue were an ftp job lands files under /home/loginid at 5:30 pm and at 6 pm we run a get file on the mvs mainframe machine ftp the file from the server to the mainframe. We get an error file is in use eventhu it is not !!... (4 Replies)
Discussion started by: mrn6430
4 Replies
8. UNIX for Advanced & Expert Users
Hi, there is a password lock problem happening everyday at one of the servers(GNU RH-Linux;kernel release version 2.6.18-308.20.1.el5) for a particular user id which is an appln user id. Everyday it needs to be reset by the owner/unix user mgmt team. My suspicion was if any cronjob was running... (3 Replies)
Discussion started by: sam_bd
3 Replies
9. Proxy Server
Details Samba server:
Release: 5.10
Kernel architecture: sun4u
Application architecture: sparc
Hardware provider: Sun_Microsystems
Kernel version: SunOS 5.10 Generic_142909-17
Samba version:
Samba version 3.5.6
Smb.conf file section Global:
# smb.conf for Airbus Industries fuer... (0 Replies)
Discussion started by: Jean-Guillaume
0 Replies
LO(4) BSD Kernel Interfaces Manual LO(4)
NAME
lo -- software loopback network interface
SYNOPSIS
pseudo-device
loop
DESCRIPTION
The loop interface is a software loopback mechanism which may be used for performance analysis, software testing, and/or local communication.
As with other network interfaces, the loopback interface must have network addresses assigned for each address family with which it is to be
used. These addresses may be set or changed with the SIOCSIFADDR ioctl(2). The loopback interface should be the last interface configured,
as protocols may use the order of configuration as an indication of priority. The loopback should never be configured first unless no hard-
ware interfaces exist.
DIAGNOSTICS
lo%d: can't handle af%d. The interface was handed a message with addresses formatted in an unsuitable address family; the packet was
dropped.
SEE ALSO
inet(4), intro(4), ns(4)
HISTORY
The lo device appeared in 4.2BSD.
BUGS
Previous versions of the system enabled the loopback interface automatically, using a nonstandard Internet address (127.1). Use of that
address is now discouraged; a reserved host address for the local network should be used instead.
4.2 Berkeley Distribution June 5, 1993 4.2 Berkeley Distribution