Delete root password
Hi i am trying to enable root access as i need to perform a check on something and it seems that there is already a root password issued. when i enabled root in netinfo then went and tried to enter a password it says inncorret password meaning there is an old password and to change it i have to enter it. i have enabled root on this machince before to do various things but i always disable it and i thought that upon disabling root it also deletes the root password you set. is there a way to delete it manually with a terminal command or something?
macbook core duo Mac OS X (10.4.8) 1.83 ghz processor, 1 gb ram
If you have an "admin" account, you could set a new password for the "root" account using 'passwd' or 'dsenableroot', i.e. either of:<pre>sudo passwd root
dsenableroot -u adminusername</pre>For that matter, are you sure there is a need to enable to "root" user at all? An "admin" account can be used for many administrative functions without resorting to "root"...
Similar Messages
-
How to Delete and Reset a Lost Root Password on a System With a Mirrored ??
hi All,
we are experiencing problem,lost root password on Solaris 10 Sparc T5120, with mirror root,
and we found the solution from Metalink.oracle.com, has anyone have try this??
here list capture the file system :
Filesystem size used avail capacity Mounted on
*/dev/md/dsk/d10 2.0G 349M 1.6G 18% /*
*/dev/md/dsk/d40 9.8G 563M 9.2G 6% /usr*
*/dev/md/dsk/d30 9.8G 1.4G 8.4G 15% /var*
*/dev/md/dsk/d50 7.9G 310M 7.5G 4% /opt*
*/dev/md/dsk/d600 3.8G 4.3M 3.8G 1% /home*
*/dev/md/dsk/d602 471M 20M 404M 5% /app/controlm*
*/dev/md/dsk/d601 471M 251M 173M 60% /app/ctsa*
*/dev/md/dsk/d604 4.9G 1.1G 3.8G 23% /app/oramon*
*/dev/md/dsk/d603 20G 11G 8.2G 58% /app/oracle*
*/dev/md/dsk/d606 39G 10.0G 29G 26% /proj/iprdb01/orafra/iprod01p*
here the step :
Solstice DiskSuite[TM] Software: How to Delete and Reset a Lost Root Password on a System With a Mirrored Root Disk [ID 1010755.1]
Solution
Steps to Follow
How to delete and reset a lost root password on a system with a mirrored root disk.
1) Insert the Solaris[TM] Operating System CD-ROM into the CD-ROM drive.
2) Once the CD-ROM is in the drive, perform a stop-a. This brings the system down to the "ok" prompt.
3) From the "ok" prompt, perform a single-user boot from the Solaris OS CD-ROM.
ok boot cdrom -s4) At the "#" prompt, determine which disk is the system's boot disk (containing the root file system). There are several Oracle architectures and various configurations of systems when it concerns a boot disk. As a general rule, most boot disks are attached to controller 0 (c0). Usually, their SCSI target is
either 3 (t3) or 0 (t0). However, Oracle machines are very flexible, and the boot disk could be at a different location. If you are not sure which disk is your boot disk, perform the following steps to determine the location of the boot device:
a) # eeprom boot-device
The output might appear to be simple, such as "disk" or "disk1" or more complicated, such as a pathname "/iommu/sbus/espdma@4,8400000/...../sd@3,0:a".
b) Make note of the boot-device. If the boot-device is a pathname, it is beyond the scope of this information to provide the location of the customized boot disk. However, for most configurations,
finding the customized boot disk is an easy task. The "Format" command shows all available disks:
#format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
(enter its number): c) Enter d to exit format.
Now, you will have an idea what disks are on the system. Therefore, if the boot-device is "disk" and format shows "c0t0d0" (on some systems "c0t3d0") then that is the boot device. If boot-device
shows "disk1" and format shows "c0t1d0," then that is the boot device. If format shows multiple disks, then based on what the "eeprom boot-device" command shows, the system's boot disk would be:
boot-device format
disk c0t0d0 or c0t3d0 (machine dependent)
disk1 c1t0d0
disk2 c0t2d0
disk3 c0t3d0 or c0t0d0 (machine dependent)
and so on ....
5) Because the system was not brought down gracefully (no root password means having to use the Stop-a keystroke to "crash" the system), you need to run "fsck" to clean the root partition (slice). The fsckalso confirms that you selected the proper slice.
# fsck /dev/rdsk/c1t0d0s0
where the X and Y are determined by the previous procedure. It is also possible to have a root partition which is not on slice 0 (s0), but, again, that is not a standard configuration.
The output of "fsck" looks like this:
** /dev/rdsk/c1t0d0s0
** last mounted on /
** Phase 1 .....
The second line in the output of "fsck" ("** Last mounted on /") confirms that this is the correct root filesystem partition. Answer "y" to any questions fsck asks. There shouldn't be too many items
needing repair. If there are, there is a possibility of a corrupted root filesystem. After fsck is finished, mount the root partition:
# mount /dev/dsk/c1t0d0s0 /a
Again, X and Y are the same as for the fsck command.
For example:
# mount /dev/dsk/c1t0d0s0 /a
6) From the root prompt, set the proper TERM type command (such as vt100, dtterm, sun, and so on)
by entering this command:
# TERM=sun; export TERM
7) Use the VI text editor to edit the /etc/shadow file:
# vi /a/etc/shadow
8) The first line of the /etc/shadow file is the one you want to modify.
It looks like this:
root:c3.yAVmYodWsc:6445::::::
9) Delete every character between the first and second colons in the first line of the file. When you finish deleting the characters, the line should look like this:
root::6445::::::
10) Press the Escape key, then enter the following to save the file and exit vi:
:wq!
11) Use the VI text editor to edit the /etc/system file andremove the "rootdev" line shown below:
# vi /a/etc/system
*rootdev:/pseudo/md@0:0,0,blk
Don't comment out the "rootdev" line. Actually remove it.
12) In the /a/etc/vfstab file, replace the lines for the system filesystem meta-devices with their underlying partitions. For example, change lines from
/dev/md/dsk/d0 /dev/md/rdsk/d0 / ufs 1 no -
to
/dev/dsk/c1t0d0s0 /dev/rdsk/c1t0d0s0 / ufs 1 no -
ONLY change the lines for root (/) and the filesystems that were affected by the actions you took in step 1 of this procedure. All other metadevices may stay as is in this file.
13) Unmount root, check the root filesystem, and then stop the system:
# cd /
# umount /a
# fsck /dev/rdsk/c1t0d0s0
# stop-a
14) Boot to single-user mode:
ok boot -swTHIS STEP IS VERY IMPORTANT; YOU MUST BOOT TO SINGLE-USER MODE TO AVOID FILESYSTEM CORRUPTION.
If the system does not boot to single user mode, you might have made a mistake in the previous steps.
15) Because the root password was cleared in an earlier step, press Return when prompted for the the root password. Once you are in single-user mode, you must clear the metamirrors and all the sub-mirrors for the root filesystem. For example, if root (/) is d0, run the following command:
# metaclear -f -r d0
Running the metaclear command not only clears the metamirror but also clears the submirrors that are part of this mirror.
16) When the metamirror is cleared, continue the boot up to multiuser mode by either pressing CTRL-D or by entering the following:
# exit
Now everything should be as it was, except that the system partition is on the underlying partition and isn't mirrored. You will simply need to re-create the metadevices for the root mirror as you had originally.
many thanksHi,
Halt your machine.
Boot with fail-safe mode.
format and list out the disks. (You can get the root & mirror disk (c#t#d#) details from /etc/lvm/md.tab of your root or mirror disk. Earlier explorer output may help)
Mount the root disk and remove the password entry in /etc/shadow
umount it.
Mount the mirror disk and remove the password entry in /etc/shadow
umount it.
reboot the server.
Hope this helps! -
Reset lost root password and now have read only filesystem
Hello,
I have recently had to reset a locked root password by booting from cdrom, mounting the first boot disk, editing the shadow file to remove root's password and rebooting the system.
The system has booted OK but, I now have a read only filesystem - everything in / cannot be edited, passwd doesnt work etc.
df -k shows the root (/) filesystem has been mounted on the physical disk I edited:
Filesystem kbytes used avail capacity Mounted on
/pci@83,4000/FJSV,ulsa@2,1/disk@0,0:a 10085836 185862 9799116 2% /
but in the vfstab it still references the disksuite metadevice:
#device device mount FS fsck mount mount
#to mount to fsck point type pass at boot options
/dev/md/dsk/d30 /dev/md/rdsk/d30 / ufs 1 no -
So, can I simply boot from CDROM again, amend the vfstab to be /dev/dsk/c0t0d0s0 (instead of /dev/md/dsk/d03) and reboot?
Any help with this is appreciated!
Thanks,
Emmadf -k should have shown root mounted on md0
e.g. on my machine
# df -k
Filesystem kbytes used avail capacity Mounted on
/dev/md/dsk/d0 8260691 4366317 3811768 54% /
what does /etc/system show for rootdev?
# grep rootdev /etc/system
* rootdev: Set the root device. This should be a fully
* rootdev:/sbus@1,f8000000/esp@0,800000/sd@3,0:a
rootdev:/pseudo/md@0:0,0,blk
Remember if this is a mirrored drive, when you boot from CD you may need to mount both sides of the mirror and make changes on both sides- otherwise the replication may not goes as expected.
Actually, I have run into problems with the modifying one side of a mirror this way. In the past Sun tech support would recommend that I break the mirror and then rebuild it once the system is up and running. So in your case you may want to boot from CD, mount the 1st disk slice, edit /etc/vfstab AND /etc/system, boot into the OS and use the various meta commands to delete and rebuild the mirror- or at least maybe to drop and reattach the 2nd 1/2 of the mirror. -
Lost root password Can't get in to reset.........Ultra 5/10 Solaris
Just bought an Ultra 5 Sun desktop at the thrift store. This thing is brand new and was still in the box. Fired it up and come to find, it has never even been configured so I did so myself. I entered a User name and then followed that with setting up a new password for the first time. The system reboots on it's own and goes to a point asking for my Name and then password. Only problem is the password will not even type into the bar that requests it. Do I need to reset it and if so how?
Hi, boot with single user mode using cmd boot cdrom -s,then use passwd cmd to change root password.if it doesn't work.mount your root slice as /a,then edit /etc/shadow file and delete root passwd entry.I hope this tip fix your problem. : )
-
Hi Guys,
I'm rather new to all this PHP and MYSQL stuff, so please bear with me. I have downloaded and installed a copy of MYSQL and PHP, and am now trying to change tohe root password, but I keep getting an error message.
I log in to MYSQL with:
/usr/local/mysql/bin/mysql
from there I type:
UPDATE mysql.user SET Password = PASSWORD('****') WHERE User = 'root';
but I keep getting an error message of:
ERROR 1142 (42000): UPDATE command denied to user ''@'localhost' for table 'user'
what have I got wrong?I've tried to follow the above advice.
I've completely deleted my MySQl on OS X Server 10.4.7 and reinstalled using the lastest package "mysql-standard-5.0.24a-osx10.4-powerpc.dmg".
I just cannot get mysql to work properly, to set my root password.
See my first attempts with Terminal below (No.1)...
MySQL Adminsitaror and CoCoa SQL connecs with no username or password.
I've also tried to follow marcs advice at http://www.entropy.ch/software/macosx/mysql/ but to no avail.
See my second attemps with Terminal below (No.2)...
If I can crack how to reinstall and setup MySQL on OS X Server 10.4.7 then I'll have a good Disaster Recovery Plan, I hope you can help, thanks.
No.1
Last login: Fri Sep 22 17:26:02 on ttyp1
Welcome to Darwin!
Server:~ admin$
Server:~ admin$ sudo /usr/local/mysql/bin/mysqld_safe --skip-grant-tables -u root &
[1] 1014
Server:~ admin$ A mysqld process already exists
[1]+ Exit 1 sudo /usr/local/mysql/bin/mysqld_safe --skip-grant-tables -u root
Server:~ admin$ sudo /Library/StartupItems/MySQLCOM/MySQLCOM stop
Stopping MySQL database server
Server:~ admin$ sudo /usr/local/mysql/bin/mysqld_safe --skip-grant-tables -u root &
[1] 1066
Server:~ admin$ Starting mysqld daemon with databases from /usr/local/mysql/data
Server:~ admin$ sudo /Library/StartupItems/MySQLCOM/MySQLCOM start
Starting MySQL database server
Server:~ admin$ /usr/local/mysql/bin/mysql -u root
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/mysql/mysql.sock' (13)
Server:~ admin$ /usr/local/mysql-standard-5.0.24a-osx10.4-powerpc/bin/mysql -u root
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/mysql/mysql.sock' (13)
Server:~ admin$
No.2
Last login: Fri Sep 22 17:26:12 on ttyp1
Welcome to Darwin!
Server:~ admin$ sudo find /usr/local/mysql/data -type f -exec rm {} ';'
Password:
Server:~ admin$
Server:~ admin$ sudo hostname 127.0.0.1
Server:~ admin$ cd /usr/local/mysql
Server:/usr/local/mysql admin$ sudo ./scripts/mysqlinstalldb
Installing all prepared tables
060922 17:35:30 [Warning] Setting lowercase_tablenames=2 because file system for /usr/local/mysql-standard-5.0.24a-osx10.4-powerpc/data/ is case insensitive
060922 17:35:30 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=127-bin' to avoid this problem.
Fill help tables
060922 17:35:31 [Warning] Setting lowercase_tablenames=2 because file system for /usr/local/mysql-standard-5.0.24a-osx10.4-powerpc/data/ is case insensitive
060922 17:35:31 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=127-bin' to avoid this problem.
To start mysqld at boot time you have to copy support-files/mysql.server
to the right place for your system
PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
To do so, start the server, then issue the following commands:
./bin/mysqladmin -u root password 'new-password'
./bin/mysqladmin -u root -h 127.0.0.1 password 'new-password'
See the manual for more instructions.
You can start the MySQL daemon with:
cd . ; ./bin/mysqld_safe &
You can test the MySQL daemon with the benchmarks in the 'sql-bench' directory:
cd sql-bench ; perl run-all-tests
Please report any problems with the ./bin/mysqlbug script!
The latest information about MySQL is available on the web at
http://www.mysql.com
Support MySQL by buying support/licenses at http://shop.mysql.com
Server:/usr/local/mysql admin$ sudo chown -R mysql data/
Server:/usr/local/mysql admin$ /usr/local/mysql/bin/mysqladmin -u root password operate
/usr/local/mysql/bin/mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket '/var/mysql/mysql.sock' (13)'
Check that mysqld is running and that the socket: '/var/mysql/mysql.sock' exists!
Server:/usr/local/mysql admin$ -
Hi mac community,
I´m a newcomer to Mac (and Linux) and I´ve had a problem related to root password.
I accidentally entered a password for root on my mac and I can´t remember it. I asked friends that work under linux for help, but they weren´t able to solve me the problem.
We´ve tried to start up the computer from the installation CD´s to delete the '*' symbol at /etc/passwd file but we failed. We either can´t do it once we are in user account. We can´t access root by any mean...
Can you help me before I set fire to my computer? ... ...
Thanks a lot.Hello sailbillo:
Welcome to Apple discussions
To save your local fire department an emergency run, read this knowledge base article:
http://docs.info.apple.com/article.html?artnum=106156
Toward the bottom you will find the steps for resetting an administrator password.
This article has more information about the root user:
http://docs.info.apple.com/article.html?artnum=106290
Barry -
I may have erased my root password now I try to install but it does not work. after mounting /dev/dsk/c0d0t0s0 /mnt I do cd /mnt. then I type the terminal and do vi. but it said that the terminal is unknown and also I can access shadow to delete the password. what do i do wrong? If somoene know the step please let me know.
ThanksHi there,
I do not know how you lost your root passwd but the following is are the steps to recover the root passwd if you have wrongfully
change the shell for the root. I am sure you can use the same steps for your purpose.
Question:
Some root users like to manually change the shell of account root. The most possible mistake is to simply change the default shell "/sbin/sh" to "/sbin/ksh". Thereafter, you will fail to log on the root because of the error of "No shell".
To fix the problem, the only way is to change root shell from /sbin/ksh to /usr/bin/ksh in /etc/passwd. Since the /etc/passwd is owned by root and you can not log on as root any more, so how to solve the problem ?
The problem is caused because the user does not know there are no other shells but Bourne Shell in /sbin. Therefore the system can not find /sbin/ksh and you fail to log on the root because of "No shell".
/sbin/sh is a hard copy under root (/) file system to make the system usable even before the file system /usr is mounted. It is very useful for system maintenance.
Below is the solution for Solaris Sparc/Intel platform respectively.
Caution: This solution can be also used to break into a system to alter security sensitive files, only authority persons can use it. Any damage caused is under your own responsibility.
For Solaris Intel platform:
1. Note down the root file system, e.g., /dev/dsk/c0t0d0s0
2. Insert installation CD
3. Reboot the system
4. Press ESC at the Press ESCape to interrupt autoboot in 5 seconds prompt.
5. Press the F2 key (F2_Continue) at the Solaris Device Configuration Assistant
screen.
6. Press the F2 key (F2_Continue) at the Identified Devices screen.
7. Select the CD-ROM drive as the boot device from the Boot Solaris screen,then press the F2 key (F2_Continue).
8. Type b -s at the Select the type of installation: prompt.
9. Mount the root file system to /a. E.g.,
# mount /dev/dsk/c0t0d0s0 /a
10. Modify /etc/passwd to correct the mistake by
vi /a/etc/passwd, then change /sbin/ksh to /usr/bin/ksh in root entity
11. Unmount the /a directory and reboot the system. -
Trouble resetting forgotten MySQL root password
Hi there,
As the title suggests, I've forgotten my MySQL root password (and where I wrote it down) and have done endless searches (Google, MySQL site and forum, etc.), tried the resolutions but have not had any luck in resetting the password.
I tried the instructions on the MySQL site, but when I did that, I got this:
I've tried removing and restarting instances, as well as uninstalling MySQL, rebooting and then re-installing; still no success.
I'm running PHP (5.3.0) and MySQL (5.1.37) on Windows Vista.
I appreciate any help anyone can offer.
Thanks,
HeatherThe simplest way that I know to deal with this situation on Windows is to uninstall MySQL. Doing so should leave the databases intact in the data folder, although you might want to copy the contents of the data folder to a different location first.
Inside the data folder is another folder called mysql. Delete it, and then reinstall MySQL. You should then be able to set up a new root password. -
Auto mounting disk drives on click without prompting root password
I've installed Arch linux using the instructions given on the Beginner's Guide wiki.
I want to auto mount a file system (partition) when I click on a partition from the default toolbar or from within nautilus, without prompting me to provide the root password for the system.
I'm using 'gdm' as one of the DAEMONS entries to start the graphical environment in /etc/rc.conf
Following the above mentioned wiki, I had deleted the '~/.xinitrc' file as it was mentioned in here.
Now, how do I find(or regenerate) a backup copy of this above mentioned file, to add the line ''exec ck-launch-session"?
Or, is there some other way to get the desired functionality working for me?As for the .xinitrc file:
@skunktrader: This is exactly what I wanted, the '/etc/skel/' directory. Never realized that directory there. Thanks!!!
@Mr.Elendig: Creating the file manually was too obvious. Thanks anyway!!
As for my requirement:
Even after placing the .xinitrc to my home directory and appending the line 'exec ck-launch-session gnome-session', I'm still being prompted for root authenication when trying to mount the partition from the desktop environment. -
Lost root password on Ultra2 Sun system and do not know the procedure to recover. I do not have any other accounts to login as. I do have installation media and do not know the procedure to boot it to try and recover that way. Solaris 2.5.1
This is a procedure I wrote up to recover roots password, give it a try. Test between the brackets are the commands you enter (without brackets).
Ritchie
1) Place the solaris software disk into cdrom drive.
2) Change machine state to PROM hardware level: [ init 0 ].
You should then see an OK prompt.
3) Boot from cdrom to single user mode: [ boot cdrom -s ].
Should eventually see a # prompt.
4) Mount the disk drive as filesystem a: [ mount /dev/dsk/c0t0d0s0 /a ].
5) Change to the a directory: [ cd /a ].
Look for the etc directory by issuing an ls command: [ ls ].
6) Switch to the etc directory: [ cd etc ].
7) Set up the machine to be able to use the vi editor by defining the terminal type for the shell:
[ TERM=vt100;export TERM ].
8) Edit the shadow file: [ vi shadow ].
a) Delete everything between the first : and the second : , which will be the encrypted password
for root.
b) Save the file: [ :wq! ].
9) Reboot the machine: [ init 0 ].
You should be at the OK prompt again.
10) Issue command to boot machine: [ boot ].
11) When CDE environment appears login as root leaving the password field blank if prompted.
12) Establish a terminal session using "this host"
13) Issue command to change the password: [ passwd ]. Confirm new password.
Now root will have the new password the next time you login. -
Snow Leopard Finder always prompting for root password
I've just 'upgraded' to Snow Leopard from Tiger on my Macbook Pro, only because increasing numbers of applications wouldn't install on Tiger. Snow Leopard is significantly slower than Tiger (2 gig plainly isn't enough for SL) and it's knackered a few of my installed applications, but that's not the main irritation. Now, when I carry out any move or delete operations in the Applications folder in Finder, I'm repeatedly prompted for the root password, even though I'm logged in as the root user. As it's quite a long password, for security reasons, this is a real PITA. Under Tiger, I was never so prompted. Can anyone suggest why Leopard's producing this prompt, and what can be done about it? Other than de-install SL and re-install Tiger, that is...
FredWilliam Boyd, Jr. wrote:
Is running as "root" your normal mode of operation? If so, why? For several reasons that's recommended.
Fred Riley wrote:
Ok, I suppose I should be a bit more accurate. I login as user 'fredriley' which is a user with superuser rights. I don't login as 'root' because that's pretty bad practice in the Unix world (and rightly so), so my original message was inaccurate.
I'm guessing that's a mistype and should say "For several reasons that's not recommended" since in OS X root is disabled by default. What you were really getting a prompt for is the admin password. But you know that.
Now, though, I find some apps that would work under Tiger not working under SL, and I see no real functionality gain from 10.4 to 10.6. Ho hum.
Only because the application versions you have were written for an OS that was superseded almost four years ago. The current versions of those apps are likely better than ever.
As for "no functionality gain" ...look harder. For me, Tiger was a good solid OS with a few annoyances, Leopard was even more solid with the refinement and removal of most of the Tiger annoyances, and Snow Leopard is a further optimization.
Some people complain about new versions of various apps and OSs only getting loaded down with feature bloat. Well, with OS X you also get a lot of refinement and optimization. If a new version appears to have "no functionality gain," would that not imply that most of the work went into substance (performance, efficiency, workflow) rather than style (feature bloat and eye candy)? Just trying to help you keep an open mind. Personally, I would not want to go back to Tiger because I would miss the subtle but positive adjustments that were made since then. Tiger would just annoy me now. -
Reset root password vCenter 6 Aappliance
Hi all,
Due to misconfigured keyboard layout, I used a wrong password for the initial installation of vCenter 6 Appliance.
Is there a chance to reset the root password? Login to Web Client with SSO [email protected] is possible.
I tried the thing with single user mode in GRUB, but there, I need also the GRUB password which is also the root password(?).
Any advice?
Thank you!
PeterI already did the same with the VMware Support, but I´m not sure if I remind every step...
Boot the Appliance VM with a Live-CD (Ubuntu,SUSE,...)
Change/set the root password to "vmware"
Mount the system disk from your vCenter appliance
In the /etc/shadow file of the live-system copy the line with the "root" entry to the /etc/shadow file of the appliance disk
Delete the old "root" line in the file
Boot the appliance an login with the "vmware" password -
I recently bought a used macbook pro. I can pretty much do everything I need on it until I want to change setting and such things. Then it asks me for an administrator password which I do not know or have. On top of that I do not have the OS disc either. Is there a way I can SAFELY reset or delete the password so I can set my own without the possibility of screwing thing up. LIke I said I can do most anything. I figured this out when attempting to tether it to my smartphone for internet access (I do all the time from my desktop but my desktop is a PC so things are a little different) I am a very new mac user, I have always been a devoted PC user until now. I have to say I am really loving my macbook pro I may just stick with mac from now on (if I can get this problem figured out without too much stress.
I am looking for the safest and best way to fix this issue where nothing I do would mess up the laptop. I can use it now and I do not want that to change, I just want to be able to change my setting and set a password of my own. PLEASE HELP, THANX!Hi
There actually is a slightly easier way in OS X 10.5 or greater.
1. Start up in single-user mode (hold Command-S as the computer starts up).
2. Type: mount -uw /
3. Press Return.
4. Type this:
passwd (user's short name)
Replace "(user's short name)" with the short name of the user account whose password you wish to reset. If you are not sure what the account name is, you can get a list of user names by typing: ls /Users
5. Press Return.
6. Enter a new user password.
7. Press Return.
8. Type: reboot
9. Press Return. -
How to delete the password in usr02 tables in mssql2005 server
hiiii..
i am using ecc6.0 and database mssql 2005 database .. all my users got locked can you please help me out that how can i delete sap* password from database...Hi,
Pls check the link.
http://help.sap.com/saphelp_nw70/helpdata/en/fc/eb3aef358411d1829f0000e829fbfe/content.htm
Anil -
Non root user can delete root files, bug?
We're having an odd permissions based problem on Solaris 10 u5 x86_64, (new install, fully patched as of 2 days ago) It means that non root users can delete root owned files, which is something I've never seen before, and I've been doing this for almost 10 years.
We're installing into an 80Gb container on VMware ESX server 3.0.1. The OS takes 20Gb (2 processors, 4Gb memory, 8Gb swap) most of the remaining 60Gb is being used as both file systems and raw devices under disksuite as soft partitions. It's one of the file systems, /apps (where we plan to install sybase) that is giving us "issues"
Essentially:
# more /etc/vfstab |grep apps
/dev/md/dsk/d0 /dev/md/rdsk/d0 /apps ufs 2 yes -
# newfs -v /dev/md/rdsk/d0
/dev/md/rdsk/d0: Unable to find Media type. Proceeding with system determined parameters.
newfs: /dev/md/rdsk/d0 last mounted as /apps
newfs: construct a new file system /dev/md/rdsk/d0: (y/n)? y
mkfs -F ufs /dev/md/rdsk/d0 20971520 -1 -1 8192 1024 264 1 546 8192 t 0 -1 8 7 n
/dev/md/rdsk/d0: Unable to find Media type. Proceeding with system determined parameters.
Warning: 4096 sector(s) in last cylinder unallocated
/dev/md/rdsk/d0: 20971520 sectors in 3414 cylinders of 48 tracks, 128 sectors
10240.0MB in 214 cyl groups (16 c/g, 48.00MB/g, 5824 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
32, 98464, 196896, 295328, 393760, 492192, 590624, 689056, 787488, 885920,
20055584, 20154016, 20252448, 20350880, 20449312, 20547744, 20646176,
20744608, 20843040, 20941472
# mount /apps
# ls -al /apps
total 20
drwxr-xr-x 3 root root 512 Sep 10 12:31 .
drwxr-xr-x 38 root root 1024 Sep 10 12:09 ..
drwx------ 2 root root 8192 Sep 10 12:31 lost+found
# su - sybase
Sun Microsystems Inc. SunOS 5.10 Generic January 2005
sol10% cd /apps
sol10% rm *
rm: lost+found is a directory
sol10% rm -rf *
rm: cannot read directory lost+found: Permission denied
sol10% ls -al
total 20
drwxr-xr-x 3 root root 512 Sep 10 12:31 .
drwxr-xr-x 38 root root 1024 Sep 10 12:09 ..
drwx------ 2 root root 8192 Sep 10 12:31 lost+found
sol10% exit
sol10% logout
# chgrp sybase /apps
# chmod g+w /apps
# ls -ald /apps
drwxrwxr-x 3 root sybase 512 Sep 10 12:31 /apps
# ls -al /apps
total 20
drwxrwxr-x 3 root sybase 512 Sep 10 12:31 .
drwxr-xr-x 38 root root 1024 Sep 10 12:09 ..
drwx------ 2 root root 8192 Sep 10 12:31 lost+found
# su - sybase
Sun Microsystems Inc. SunOS 5.10 Generic January 2005
sol10% cd /apps
sol10% rm -rf *
sol10% ls -al
total 4
drwxrwxr-x 2 root sybase 512 Sep 10 12:34 .
drwxr-xr-x 38 root root 1024 Sep 10 12:09 ..
sol10% id
uid=***(sybase) gid=***(sybase)
sol10% exit
sol10% logout
# pwd
# ls -ald /apps
drwxrwxr-x 2 root sybase 512 Sep 10 12:34 /apps
# ls -al /apps
total 4
drwxrwxr-x 2 root sybase 512 Sep 10 12:34 .
drwxr-xr-x 38 root root 1024 Sep 10 12:09 ..
It's a new "bare metal" (in as much as there is no metal) install. I created the sybase user from scratch by hand editing passwd, group and shadow, buy copying and pasting the data out of the NIS maps. All I've done besides the install & patch is setup networking manually, and created the metadb's and the soft partitions and the mount points & newfs'ed & mounted three of them . I then changed ownership of /apps to be sybase:sybase, and handed it to the database team for the sybase install. they came back and said "should we be able to do this?" as they habitually run rm rf * knowing they can't delete root owned files, only now they can... This is true even if I just chgrp the directory and give them group write permissions. They can still delete anything owned by root, even if it doesn't have group permissions just like the lost+found directory. No other "real" machine we have, x86 or SPARC does this, but we've never installed u5 before either.
As you can imagine losing the lost+found directory is a bit of a problem, however what's really worrying me is if they can do that, what happens when they run sybase as the sybase user? If it borks can they trash the OS and write/overwrite random files?
It's a VM, so in as much that's not a problem, but the reason it's a VM is somebody wants to send a VM to a client as a demo, and at present it's highly unstable IMO.
Does anyone have any idea where to start? My thoughts are that it may be a VMware issue, (though the hardware and the guest OS is supported) it could be a bug, because I've never seen that weird newfs error before, and then I found this:
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6622243
Or it could be me, and the fact that I'm hand configuring it, and u5 now requires I do it "properly" with useradd, etc. I'd like to test, but the guy wants it built, and wants it now, so I patched it up, and gave it back to the database team and told them to be careful.
I'd be interested in you opinions regardless.
The full spec of the "machine" is below, sol10 is not it's name for obvious reasons, and I've hashed out the ID & GIUD for similar reasons.
# uname -a
SunOS sol10 5.10 Generic_127128-11 i86pc i386 i86pc
# prtdiag
System Configuration: VMware, Inc. VMware Virtual Platform
BIOS Configuration: Phoenix Technologies LTD 6.00 09/06/2007
==== Processor Sockets ====================================
Version Location Tag
Pentium(R) Pro CPU socket #0
Pentium(R) Pro CPU socket #1
==== Memory Device Sockets ================================
Type Status Set Device Locator Bank Locator
DRAM in use 0 RAM slot #0 RAM slot #0
DRAM in use 0 RAM slot #1 RAM slot #1
DRAM in use 0 RAM slot #2 RAM slot #2
DRAM in use 0 RAM slot #3 RAM slot #3
==== On-Board Devices =====================================
VMware SVGA II
ES1371
==== Upgradeable Slots ====================================
ID Status Type Description
0 unknown ISA ISA Slot J8
0 unknown ISA ISA Slot J9
0 unknown ISA ISA Slot J10
1 in use PCI PCI Slot J11
2 in use PCI PCI Slot J12
3 in use PCI PCI Slot J13
4 available PCI PCI Slot J14
# dmesg
Wednesday, 10 September 2008 15:33:35 BST
Sep 10 10:17:44 sol10 busra: [ID 490441 kern.info] NOTICE: ndi_ra_free: bad free, dip ffffffff803807a8, resource type memory
Sep 10 10:17:44 sol10 busra: [ID 883242 kern.info] NOTICE: ndi_ra_free: freeing base 0xe0000, len 0x4000 overlaps with existing resource base 0x0, len 0xf4000000
Sep 10 10:17:44 sol10 rootnex: [ID 349649 kern.info] pci0 at root: space 0 offset 0
Sep 10 10:17:44 sol10 genunix: [ID 936769 kern.info] pci0 is /pci@0,0
Sep 10 10:17:44 sol10 scsi: [ID 365881 kern.info] /pci@0,0/pci1000,30@10 (mpt0):
Sep 10 10:17:44 sol10 Rev. 1 LSI, Inc. 1030 found.
Sep 10 10:17:44 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: pci1000,30 (mpt) instance 0 vector 0x11 ioapic 0x2 intin 0x11 is bound to cpu 0
Sep 10 10:17:44 sol10 scsi: [ID 365881 kern.info] /pci@0,0/pci1000,30@10 (mpt0):
Sep 10 10:17:44 sol10 mpt0 Firmware version v0.0.0.0 (?)
Sep 10 10:17:44 sol10 scsi: [ID 365881 kern.info] /pci@0,0/pci1000,30@10 (mpt0):
Sep 10 10:17:44 sol10 mpt0: IOC Operational.
Sep 10 10:17:44 sol10 pci: [ID 370704 kern.info] PCI-device: pci1000,30@10, mpt0
Sep 10 10:17:44 sol10 genunix: [ID 936769 kern.info] mpt0 is /pci@0,0/pci1000,30@10
Sep 10 10:17:44 sol10 scsi: [ID 193665 kern.info] sd0 at mpt0: target 0 lun 0
Sep 10 10:17:44 sol10 genunix: [ID 936769 kern.info] sd0 is /pci@0,0/pci1000,30@10/sd@0,0
Sep 10 10:17:44 sol10 genunix: [ID 408114 kern.info] /pci@0,0/pci1000,30@10/sd@0,0 (sd0) online
Sep 10 10:17:44 sol10 unix: [ID 190185 kern.info] SMBIOS v2.31 loaded (1695 bytes)
Sep 10 10:17:44 sol10 genunix: [ID 408114 kern.info] /cpus (cpunex0) online
Sep 10 10:17:44 sol10 pseudo: [ID 129642 kern.info] pseudo-device: dld0
Sep 10 10:17:44 sol10 genunix: [ID 936769 kern.info] dld0 is /pseudo/dld@0
Sep 10 10:17:44 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: i8042 (i8042) instance 0 vector 0x1 ioapic 0x2 intin 0x1 is bound to cpu 1
Sep 10 10:17:44 sol10 pcplusmp: [ID 398438 kern.info] pcplusmp: i8042 (i8042) instance #0 vector 0xc ioapic 0x2 intin 0xc is bound to cpu 1
Sep 10 10:17:44 sol10 i8042: [ID 526150 kern.info] 8042 device: keyboard@0, kb8042 # 0
Sep 10 10:17:44 sol10 genunix: [ID 936769 kern.info] kb80420 is /isa/i8042@1,60/keyboard@0
Sep 10 10:17:44 sol10 i8042: [ID 526150 kern.info] 8042 device: mouse@1, mouse8042 # 0
Sep 10 10:17:44 sol10 genunix: [ID 936769 kern.info] mouse80420 is /isa/i8042@1,60/mouse@1
Sep 10 10:17:44 sol10 unix: [ID 950921 kern.info] cpu0: x86 (GenuineIntel family 6 model 15 step 8 clock 2000 MHz)
Sep 10 10:17:44 sol10 unix: [ID 950921 kern.info] cpu0: Intel(r) Xeon(r) CPU E5335 @ 2.00GHz
Sep 10 10:17:47 sol10 unix: [ID 950921 kern.info] cpu1: x86 (GenuineIntel family 6 model 15 step 8 clock 2000 MHz)
Sep 10 10:17:47 sol10 unix: [ID 950921 kern.info] cpu1: Intel(r) Xeon(r) CPU E5335 @ 2.00GHz
Sep 10 10:17:47 sol10 unix: [ID 557827 kern.info] cpu1 initialization complete - online
Sep 10 10:17:47 sol10 rootnex: [ID 349649 kern.info] iscsi0 at root
Sep 10 10:17:47 sol10 genunix: [ID 936769 kern.info] iscsi0 is /iscsi
Sep 10 10:17:52 sol10 genunix: [ID 454863 kern.info] dump on /dev/dsk/c1t0d0s1 size 8197 MB
Sep 10 10:17:53 sol10 pci: [ID 370704 kern.info] PCI-device: pci8086,7191@1, pci_pci0
Sep 10 10:17:53 sol10 genunix: [ID 936769 kern.info] pci_pci0 is /pci@0,0/pci8086,7191@1
Sep 10 10:17:54 sol10 mac: [ID 469746 kern.info] NOTICE: e1000g0 registered
Sep 10 10:17:54 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: pci8086,100f (e1000g) instance 0 vector 0x12 ioapic 0x2 intin 0x12 is bound to cpu 0
Sep 10 10:17:54 sol10 e1000g: [ID 766679 kern.info] Intel(R) PRO/1000 Network Connection, Driver Ver. 5.1.11
Sep 10 10:17:54 sol10 pseudo: [ID 129642 kern.info] pseudo-device: zfs0
Sep 10 10:17:54 sol10 genunix: [ID 936769 kern.info] zfs0 is /pseudo/zfs@0
Sep 10 10:17:55 sol10 pseudo: [ID 129642 kern.info] pseudo-device: pm0
Sep 10 10:17:55 sol10 genunix: [ID 936769 kern.info] pm0 is /pseudo/pm@0
Sep 10 10:17:55 sol10 pseudo: [ID 129642 kern.info] pseudo-device: power0
Sep 10 10:17:55 sol10 genunix: [ID 936769 kern.info] power0 is /pseudo/power@0
Sep 10 10:17:56 sol10 pseudo: [ID 129642 kern.info] pseudo-device: devinfo0
Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] devinfo0 is /pseudo/devinfo@0
Sep 10 10:17:56 sol10 rootnex: [ID 349649 kern.info] xsvc0 at root
Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] xsvc0 is /xsvc
Sep 10 10:17:56 sol10 pseudo: [ID 129642 kern.info] pseudo-device: pseudo1
Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] pseudo1 is /pseudo/zconsnex@1
Sep 10 10:17:56 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: lp (ecpp) instance 0 vector 0x7 ioapic 0x2 intin 0x7 is bound to cpu 1
Sep 10 10:17:56 sol10 isa: [ID 202937 kern.info] ISA-device: ecpp0
Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] ecpp0 is /isa/lp@1,378
Sep 10 10:17:56 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: asy (asy) instance 0 vector 0x4 ioapic 0x2 intin 0x4 is bound to cpu 0
Sep 10 10:17:56 sol10 isa: [ID 202937 kern.info] ISA-device: asy0
Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] asy0 is /isa/asy@1,3f8
Sep 10 10:17:56 sol10 pcplusmp: [ID 398438 kern.info] pcplusmp: asy (asy) instance #1 vector 0x3 ioapic 0x2 intin 0x3 is bound to cpu 0
Sep 10 10:17:56 sol10 isa: [ID 202937 kern.info] ISA-device: asy1
Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] asy1 is /isa/asy@1,2f8
Sep 10 10:17:56 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: ide (ata) instance 0 vector 0xe ioapic 0x2 intin 0xe is bound to cpu 1
Sep 10 10:17:56 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: ide (ata) instance 0 vector 0xe ioapic 0x2 intin 0xe is bound to cpu 0
Sep 10 10:17:56 sol10 genunix: [ID 640982 kern.info] ATAPI device at targ 0, lun 0 lastlun 0x0
Sep 10 10:17:56 sol10 genunix: [ID 846691 kern.info] model VMware Virtual IDE CDROM Drive
Sep 10 10:17:56 sol10 genunix: [ID 479077 kern.info] ATA/ATAPI-4 supported, majver 0x1e minver 0x17
Sep 10 10:17:56 sol10 pci: [ID 370704 kern.info] PCI-device: ide@0, ata0
Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] ata0 is /pci@0,0/pci-ide@7,1/ide@0
Sep 10 10:17:56 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
Sep 10 10:17:56 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
Sep 10 10:17:56 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
Sep 10 10:17:56 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
Sep 10 10:17:56 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
Sep 10 10:17:56 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
Sep 10 10:17:56 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
Sep 10 10:17:56 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
Sep 10 10:17:56 sol10 scsi: [ID 193665 kern.info] sd1 at ata0: target 0 lun 0
Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] sd1 is /pci@0,0/pci-ide@7,1/ide@0/sd@0,0
Sep 10 10:17:56 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: fdc (fdc) instance 0 vector 0x6 ioapic 0x2 intin 0x6 is bound to cpu 1
Sep 10 10:17:56 sol10 isa: [ID 202937 kern.info] ISA-device: fdc0
Sep 10 10:17:56 sol10 fdc: [ID 114370 kern.info] fd0 at fdc0
Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] fd0 is /isa/fdc@1,3f0/fd@0,0
Sep 10 10:17:56 sol10 genunix: [ID 314293 kern.info] device pciclass,030000@f(display#0) keeps up device sd@0,0(sd#1), but the latter is not power managed
Sep 10 10:17:56 sol10 pseudo: [ID 129642 kern.info] pseudo-device: nvidia255
Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] nvidia255 is /pseudo/nvidia@255
Sep 10 10:17:56 sol10 pseudo: [ID 129642 kern.info] pseudo-device: ramdisk1024
Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] ramdisk1024 is /pseudo/ramdisk@1024
Sep 10 10:17:56 sol10 pseudo: [ID 129642 kern.info] pseudo-device: lockstat0
Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] lockstat0 is /pseudo/lockstat@0
Sep 10 10:17:56 sol10 pseudo: [ID 129642 kern.info] pseudo-device: llc10
Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] llc10 is /pseudo/llc1@0
Sep 10 10:17:56 sol10 pseudo: [ID 129642 kern.info] pseudo-device: lofi0
Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] lofi0 is /pseudo/lofi@0
Sep 10 10:17:56 sol10 pseudo: [ID 129642 kern.info] pseudo-device: dtrace0
Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] dtrace0 is /pseudo/dtrace@0
Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: profile0
Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] profile0 is /pseudo/profile@0
Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: systrace0
Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] systrace0 is /pseudo/systrace@0
Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: fbt0
Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] fbt0 is /pseudo/fbt@0
Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: sdt0
Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] sdt0 is /pseudo/sdt@0
Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: fasttrap0
Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] fasttrap0 is /pseudo/fasttrap@0
Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: fcp0
Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] fcp0 is /pseudo/fcp@0
Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: fcsm0
Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] fcsm0 is /pseudo/fcsm@0
Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: lx_systrace0
Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] lx_systrace0 is /pseudo/lx_systrace@0
Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: ucode0
Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] ucode0 is /pseudo/ucode@0
Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: fssnap0
Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] fssnap0 is /pseudo/fssnap@0
Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: winlock0
Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] winlock0 is /pseudo/winlock@0
Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: vol0
Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] vol0 is /pseudo/vol@0
Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: rsm0
Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] rsm0 is /pseudo/rsm@0
Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: pool0
Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] pool0 is /pseudo/pool@0
Sep 10 10:17:57 sol10 ipf: [ID 774698 kern.info] IP Filter: v4.1.9, running.
Sep 10 10:18:05 sol10 nfs4cbd[395]: [ID 867284 daemon.notice] nfsv4 cannot determine local hostname binding for transport tcp - delegations will not be available on this transport
Sep 10 10:18:10 sol10 sendmail[598]: [ID 702911 mail.crit] My unqualified host name (localhost) unknown; sleeping for retry
Sep 10 10:18:10 sol10 sendmail[600]: [ID 702911 mail.crit] My unqualified host name (localhost) unknown; sleeping for retry
Sep 10 10:18:17 sol10 mac: [ID 736570 kern.info] NOTICE: e1000g0 unregistered
Sep 10 10:19:10 sol10 sendmail[598]: [ID 702911 mail.alert] unable to qualify my own domain name (localhost) -- using short name
Sep 10 10:19:10 sol10 sendmail[600]: [ID 702911 mail.alert] unable to qualify my own domain name (localhost) -- using short name
Sep 10 10:20:10 sol10 pseudo: [ID 129642 kern.info] pseudo-device: devinfo0
Sep 10 10:20:10 sol10 genunix: [ID 936769 kern.info] devinfo0 is /pseudo/devinfo@0
Sep 10 10:24:54 sol10 mac: [ID 469746 kern.info] NOTICE: e1000g0 registered
Sep 10 10:24:54 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: pci8086,100f (e1000g) instance 0 vector 0x12 ioapic 0x2 intin 0x12 is bound to cpu 0
Sep 10 10:24:54 sol10 e1000g: [ID 766679 kern.info] Intel(R) PRO/1000 Network Connection, Driver Ver. 5.1.11
Sep 10 10:24:59 sol10 e1000g: [ID 801725 kern.info] NOTICE: pci8086,100f - e1000g[0] : Adapter 1000Mbps full duplex copper link is up.
Sep 10 10:28:21 sol10 in.routed[502]: [ID 798604 daemon.error] empty response from 129.0.1.124
Sep 10 10:35:17 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
Sep 10 10:35:17 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
Sep 10 10:35:17 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
Sep 10 10:35:17 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
Sep 10 10:35:17 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
Sep 10 10:35:17 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
Sep 10 10:35:17 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
Sep 10 10:35:17 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
Sep 10 10:35:17 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: lp (ecpp) instance 0 vector 0x7 ioapic 0x2 intin 0x7 is bound to cpu 1
Sep 10 10:35:17 sol10 isa: [ID 202937 kern.info] ISA-device: ecpp0
Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] ecpp0 is /isa/lp@1,378
Sep 10 10:35:17 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: asy (asy) instance 0 vector 0x4 ioapic 0x2 intin 0x4 is bound to cpu 0
Sep 10 10:35:17 sol10 isa: [ID 202937 kern.info] ISA-device: asy0
Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] asy0 is /isa/asy@1,3f8
Sep 10 10:35:17 sol10 pcplusmp: [ID 398438 kern.info] pcplusmp: asy (asy) instance #1 vector 0x3 ioapic 0x2 intin 0x3 is bound to cpu 0
Sep 10 10:35:17 sol10 isa: [ID 202937 kern.info] ISA-device: asy1
Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] asy1 is /isa/asy@1,2f8
Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: nvidia255
Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] nvidia255 is /pseudo/nvidia@255
Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: ramdisk1024
Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] ramdisk1024 is /pseudo/ramdisk@1024
Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: lockstat0
Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] lockstat0 is /pseudo/lockstat@0
Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: llc10
Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] llc10 is /pseudo/llc1@0
Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: lofi0
Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] lofi0 is /pseudo/lofi@0
Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: profile0
Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] profile0 is /pseudo/profile@0
Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: systrace0
Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] systrace0 is /pseudo/systrace@0
Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: fbt0
Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] fbt0 is /pseudo/fbt@0
Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: sdt0
Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] sdt0 is /pseudo/sdt@0
Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: fcp0
Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] fcp0 is /pseudo/fcp@0
Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: fcsm0
Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] fcsm0 is /pseudo/fcsm@0
Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: lx_systrace0
Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] lx_systrace0 is /pseudo/lx_systrace@0
Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: ucode0
Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] ucode0 is /pseudo/ucode@0
Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: fssnap0
Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] fssnap0 is /pseudo/fssnap@0
Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: winlock0
Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] winlock0 is /pseudo/winlock@0
Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: pm0
Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] pm0 is /pseudo/pm@0
Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: rsm0
Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] rsm0 is /pseudo/rsm@0
Sep 10 10:55:50 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
Sep 10 10:55:50 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
Sep 10 10:55:50 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
Sep 10 10:55:50 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
Sep 10 10:55:50 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
Sep 10 10:55:50 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
Sep 10 10:55:50 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
Sep 10 10:55:50 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
Sep 10 11:28:55 sol10 in.routed[502]: [ID 798604 daemon.error] empty response from 129.0.1.124
Sep 10 12:28:56 sol10 in.routed[502]: [ID 798604 daemon.error] empty response from 129.0.1.124
Sep 10 13:29:01 sol10 in.routed[502]: [ID 798604 daemon.error] empty response from 129.0.1.124
Sep 10 14:29:10 sol10 in.routed[502]: [ID 798604 daemon.error] empty response from 129.0.1.124
Sep 10 15:29:38 sol10 in.routed[502]: [ID 798604 daemon.error] empty response from 129.0.1.124
# prtconf
System Configuration: Sun Microsystems i86pc
Memory size: 4132 Megabytes
System Peripherals (Software Nodes):
i86pc
scsi_vhci, instance #0
isa, instance #0
i8042, instance #0
keyboard, instance #0
mouse, instance #0
lp, instance #0
asy, instance #0
asy, instance #1
fdc, instance #0
fd, instance #0
pci, instance #0
pci15ad,1976 (driver not attached)
pci8086,7191, instance #0
pci15ad,1976 (driver not attached)
pci-ide, instance #0
ide, instance #0
sd, instance #1
ide (driver not attached)
pci15ad,1976 (driver not attached)
display, instance #0
pci1000,30, instance #0
sd, instance #0
pci15ad,750, instance #0
iscsi, instance #0
pseudo, instance #0
options, instance #0
agpgart, instance #0
xsvc, instance #0
objmgr, instance #0
acpi (driver not attached)
used-resources (driver not attached)
cpus, instance #0
cpu (driver not attached)
cpu (driver not attached)
# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <DEFAULT cyl 10440 alt 2 hd 255 sec 63>
/pci@0,0/pci1000,30@10/sd@0,0
Specify disk (enter its number): 0
selecting c1t0d0
[disk formatted]
Warning: Current Disk has mounted partitions.
/dev/dsk/c1t0d0s0 is currently mounted on /. Please see umount(1M).
/dev/dsk/c1t0d0s1 is currently used by swap. Please see swap(1M).
/dev/dsk/c1t0d0s3 is currently mounted on /usr. Please see umount(1M).
/dev/dsk/c1t0d0s4 is currently mounted on /var. Please see umount(1M).
/dev/dsk/c1t0d0s5 is currently mounted on /opt. Please see umount(1M).
/dev/dsk/c1t0d0s6 is part of SVM volume sp:d8. Please see metaclear(1M).
/dev/dsk/c1t0d0s7 contains an SVM mdb. Please see metadb(1M).
FORMAT MENU:
disk - select a disk
type - select (define) a disk type
partition - select (define) a partition table
current - describe the current disk
format - format and analyze the disk
fdisk - run the fdisk program
repair - repair a defective sector
label - write label to the disk
analyze - surface analysis
defect - defect list management
backup - search for backup labels
verify - read and display labels
save - save new disk/partition definitions
inquiry - show vendor, product and revision
volname - set 8-character volume name
!<cmd> - execute <cmd>, then return
quit
format> p
PARTITION MENU:
0 - change `0' partition
1 - change `1' partition
2 - change `2' partition
3 - change `3' partition
4 - change `4' partition
5 - change `5' partition
6 - change `6' partition
7 - change `7' partition
select - select a predefined table
modify - modify a predefined partition table
name - name the current table
print - display the current table
label - write partition map and label to the disk
!<cmd> - execute <cmd>, then return
quit
partition> p
Current partition table (original):
Total disk cylinders available: 10440 + 2 (reserved cylinders)
Part Tag Flag Cylinders Size Blocks
0 root wm 1 - 131 1.00GB (131/0/0) 2104515
1 swap wu 132 - 1176 8.01GB (1045/0/0) 16787925
2 backup wm 0 - 10439 79.97GB (10440/0/0) 167718600
3 usr wm 1177 - 1829 5.00GB (653/0/0) 10490445
4 var wm 1830 - 2091 2.01GB (262/0/0) 4209030
5 unassigned wm 2092 - 2614 4.01GB (523/0/0) 8401995
6 unassigned wm 2617 - 10439 59.93GB (7823/0/0) 125676495
7 unassigned wm 2615 - 2616 15.69MB (2/0/0) 32130
8 boot wu 0 - 0 7.84MB (1/0/0) 16065
9 unassigned wm 0 0 (0/0/0) 0
partition> quit
FORMAT MENU:
disk - select a disk
type - select (define) a disk type
partition - select (define) a partition table
current - describe the current disk
format - format and analyze the disk
fdisk - run the fdisk program
repair - repair a defective sector
label - write label to the disk
analyze - surface analysis
defect - defect list management
backup - search for backup labels
verify - read and display labels
save - save new disk/partition definitions
inquiry - show vendor, product and revision
volname - set 8-character volume name
!<cmd> - execute <cmd>, then return
quit
format> q
# metastat -p
d8 -p c1t0d0s6 -o 109973513 -b 61440
d7 -p c1t0d0s6 -o 109461512 -b 512000
d6 -p c1t0d0s6 -o 109051911 -b 409600
d5 -p c1t0d0s6 -o 88080390 -b 20971520
d4 -p c1t0d0s6 -o 67108869 -b 20971520
d3 -p c1t0d0s6 -o 46137348 -b 20971520
d2 -p c1t0d0s6 -o 41943043 -b 4194304
d1 -p c1t0d0s6 -o 20971522 -b 20971520
d0 -p c1t0d0s6 -o 1 -b 20971520An easy way to think of it is this -- everything in Unix is a file. Including directories; they are just a file which contains a list of the files in that directory, and pointers to them.
If the 'sybase' user has write permission on the directory, they have permission to edit that "list", and can add or remove files to the list. It doesn't matter who the files on the list belong to, because the files are not what is being modified. Only the list of files is being modified. (Of course, in Unix, if you erase the file's listing from all of the lists it's on, the file itself goes away for housekeeping purposes.)
One thing that would have stopped the 'sybase' user from removing the lost+found directory is if that directory itself had files in it -- without write permission to the lost+found directory, that user could not have removed those files, and since one cannot remove a non-empty directory, that operation would have failed. Since lost+found was empty in this case, it could be removed simply by having permission to write to the /apps directory.
This behavior does change if you set the sticky bit on the directory -- in that case, files may only be removed by the owner of the file or directory, or if the user has write permission to the file. This would have prevented the sybase user from removing the lost+found directory. (Note, this also applies to the 'rename' function call.) This would probably be the best way to handle your situation, since you apparently do want the sybase user to be able to add files to /apps, but do not want them to be able to remove lost+found.
Edited by: MadBishop on Sep 12, 2008 7:46 AM
Maybe you are looking for
-
Since upgrading my iPhone 4 to the new ios6 software I can no longer access itunes through the itunes app. I there a fix for this yet?
-
How do I add multiple passwords to a FileVault2 external hard disk?
Hello, On a boot volume, multiple users can have access to decrypt the disk - but with external disks it appears as though only a single password can grant access. How can I enable a second passphrase to unlock a hard disk? Thanks.
-
What happened to the Save Frame As... on the File menu? It was there in FF 3.6; it's absent now.
My data source is a daily table on a Web page. In FF 3.16 I click in the table and select File>Save Frame As.... In the Save As dialog box, I key a file name ending in ".txt". The data is saved in a tab-separated text file that I open in Excel. In FF
-
HT6208 I have enough space for the recent update but it won't update??? ***? How do I fix this?
I have enough storage for the update but I cannot get it to update?? Anyone have the same problem?
-
Hi Guys, I m developing one s/w in forms 10g. my old data is in MS Access 97. I like to manipulate data in access as wel as in oracle. I installed oracle 9i database with Tramparent gateway to use non oracle database. I can manipulate data from sqlpl