Welcome to SafdarMirza.com
session controller lxdw, lxdi ....
Everyone once a while, when I wanted to reboot my windows xp workstation, I was getting a hung process window saying "Sesssion Controller lxdw" not responding. After a lot of surfing on the net and looking for a solution, I finallay found the solution when I searched my computer for files "lxdw" and found that the process is associated with "Lexmark 7600 printer". I am now in process of removing all lexmark programs, as I no longer use this printer.
Karachi History
http://www.paklinks.com/gs/
Indian (bollywood) Movies TheatresFollowing listed movie theatre offer indian (bollywood) movies showtimes in Chicago area. Regal Cantera Stadium 17 in Warrenville - 28250 Diehl Road, Warrenville, IL - (630) 836-8265 AMC South Barrington 30 in South Barrington - 175 Studio Drive, South Barrington, IL - (888) 262-4386 Big Cinemas Golf Glen 5 in Niles (no website available) - 9180 West Golf Road, Niles, IL 60714 - (847)299-2402 Last Updated (Tuesday, 20 December 2011 18:46) Managing Non-Login and Locked Solaris Accountshttp://blogs.oracle.com/gbrunett/entry/managing_non_login_and_locked
Managing Non-Login and Locked Solaris AccountsBy user12606733 on Sep 21, 2004
Today's entry will focus on enhancements to the passwd(1) command to better support the distinction between locked and non-login accounts. Specifically, we will be looking at the new -u and -N options to the passwd(1) command as well as how they relate to the much older -l option. These new capabilities will help administrators obtain better control over how their accounts are accessed and how they can in fact manage those accounts. In the past, some of the interfaces discussed below could only be achieved through manual editing of password files. The addition of these new command line options provides a much safer option for administrators to use.
While the distinction between non-login and locked accounts has existed in Solaris for many years, it became more pronounced in Solaris 9 where the semantics of locked accounts were more rigidly enforced.
Many customers noticed, for example, that locked accounts could no longer execute jobs using cron(1M). This problem was exacerbated by the fact that many commonly referenced security recommendation guides tell users to lock all of the accounts to which interactive access was not needed (which is most of the default accounts). When this was done, cron jobs for accounts such as "sys" (used for collecting system activity records) stopped working. This problem highlighted the intended difference between non-login and locked accounts and the need for additional interfaces to control them.
For those not already aware, a non-login account is one that must exist on the system (to provide a UID for example) but should not be allowed to login to a system interactively. That is, while a non-login account may be able to leverage delayed execution mechanism such as cron(1M), they cannot access the system using login(1), telnet(1) ftp(1), ssh(1), etc. Accounts that are non-login will have the token NP as their password. You can also identify non-login accounts using the passwd(1) command:
# passwd -s daemon daemon NL # grep "\^daemon:" /etc/shadow daemon:NP:6445::::::
In this case, the daemon account has been configured as a non-login account.
A locked account on the other hand is one that is not permitted to access the system in any way - it is locked. A locked account differs from one marked as non-login in that locked accounts are not permitted to use delayed execution methods like cron(1M). Locked accounts are those whose password string has the prefix \*LK\*. Further, you can identify locked accounts using the passwd(1) command:
# passwd -s listen listen LK # grep "\^listen:" /etc/shadow listen:\*LK\*:::::::
In this case, the listen account has been locked.
Here is a practical example. In this case, I will add a new account gmb to the system. By default, new accounts created using useradd(1M) are locked. After assigning a new password, I will demonstrate the use and result of the new -N and -u options to the passwd(1) command in addition to the -l option which has been around for ever.
First, let's create a test account called gmb. You will notice that by default the account will be locked.
# useradd -d /export/home/gmb gmb # passwd -s gmb gmb LK
Next, a password will be assigned to the gmb account in the usual way using the passwd(1) command...
# passwd gmb New Password: Re-enter new Password: passwd: password successfully changed for gmb # passwd -s gmb gmb PS # grep "\^gmb:" /etc/shadow gmb:Onk28eSYhYJ8s:12683::::::
You will notice that the "passwd -s" command now returns the keyword PS for "password set". If the account did not have a password defined, the keyword NP (for "no password") would have been returned.
Now that we have a password, let's lock the account and see what happens to the password string in /etc/shadow as well as to the output of "passwd -s":
# passwd -l gmb passwd: password information changed for gmb # passwd -s gmb gmb LK # grep "\^gmb:" /etc/shadow gmb:\*LK\*Onk28eSYhYJ8s:12683::::::
You will notice that the account was in fact locked, but what is new in Solaris 10 is that the password string is not replaced with the "\*LK\*" value. Instead, a "\*LK\*" string prefix is prepended to the password so that the original value can be kept if desired. The great thing about this is that it does not depend on the password algorithm used. With the addition of flexible crypt in Solaris 9, you can replace the default crypt algorithm with either others provided by default in Solaris or one of your own and this new locking mechanism will still just work.
To unlock a locked account, you just use the new "-u" option to the passwd(1) command: # passwd -u gmb passwd: password information changed for gmb # passwd -s gmb gmb PS # grep "\^gmb:" /etc/shadow gmb:Onk28eSYhYJ8s:12683::::::
The account is now unlocked and the "\*LK\*" prefix has been removed from the user's password string. The last thing that we will look at today is how you create a non-login account. To do this, simply use the "-N" option to the password command: # passwd -N gmb passwd: password information changed for gmb # passwd -s gmb gmb NL # grep "\^gmb:" /etc/shadow gmb:NP:12683::::::
You will notice that the user's original password has been removed and replaced with the string "NP". This account is now a non-login account and the original password has been discarded. You will not be able to login to this account, but the account will be able to make use of delayed execution facilities. To re-enable an account for interactive logins, simply reassign a password to the account using the passwd(1) command.
That's all for this installment. I hope you find this kind of information useful. In future installments, I will continue to highlight some of the lesser known enhancements that contribute to Solaris security in the hopes of raising awareness and their use.
Technorati Tag: OpenSolaris Solaris security SB800 SB900 Optical SlaveRef: http://strobist.blogspot.com/2010/03/q-how-to-use-your-nikon-sb-900-in.html
Q&A: How to Use Your Nikon SB-900 in Optical Slave Mode As most of you know, the discontinued Nikon SB-800 speedlight has an awesome -- yet, oddly undocumented -- built-in slave. But given the questions I have gotten recently, many people who own the newer SB-900s are not aware that their flash has the same capability.A walk-thru on how to access and use the built-in slave in your Nikon SB-900 speedlight, and how to get better results from any slave outdoors, inside. __________ SU-4 Mode Button Sequence SU-4 mode is a legacy TTL mode which existed long before Nikon's CLS system. Props to Nikon for continuing to include it. And the day they stop including it is the day I start hoarding old flashes. By setting your flash into both manual and SU-4 modes, as they say,dis where da magic happen. Here's how to do it. 1. Press the "OK" button until you see a custom function menu appear. Should take a couple of seconds. 2. Using the command dial, scroll until you get to "SU-4" mode, and press "OK". 3. Use the same dial. scroll to "on." Press "OK" again. 4. Press "Exit" to get out of the menu. 5. Set your selector switch to "Remote". You are now in SU-4 slaved mode, but you flash may be in either Manual or Automatic firing mode. You almost certainly want Manual mode. Use the "mode" button to get to "M" (or manual) mode. Now your flash is in manual mode, and set to fire when it sees another flash. You can adjust the power level in manual mode the same way you do it if you were not in SU-4 mode. __________ Tips on Usage The slave eye is just below the battery door, and is seen as a small, bright circle in the photo at left. You need to position your flash to where the head points where you want, and the eye points toward the flash which will trip this flash.(That's why the 180-degree rotation feature is valuable on the SB-900, and why you may want to add the same feature to your SB-800.) If you read the SB-800 SU-4 tutorial, you know just how good this slave is. I count on them all the time, and they rarely let me down. If I am shooting in a room with all SB-800s, I will usually only take one set of PWs and slave the other flashes. They rock. Here is how you can improve your already good results when shooting outside. When you get a misfire, the problem is usually that the slave eye window was seeing bright sun in addition to your other flash's pop. This is easy to fix. Once you get your lights set, use some gaffer's tape and make a little "porch roof" for your slave eye that will shade the sun but not block the view to the flash being used to trip this one. Your percentages will increase dramatically. And, Speaking of Master Flash One common mistake when using SB-800s or SB-900s in SU-4 mode (or any other flash with a good slave, for that matter) is not taking into account any "preflashes" that may be happening before your main exposure. These slaves are so good they will almost certainly see and preflashes from the master flash and trip your slaved flash, too. And this all happens just a few milliseconds before your exposure, so the flash does not have time to recharge and pop again when you want it to. The fix is easy -- make sure your "master" flash is not set to "master" mode, which enables a series of TTL-measuring TTL preflashes. You want all flashes in manual, where they will issue just one, pre-set pop. This way all of your flashes will sync together, and exactly when you want. As long as everything is set to manual, your secondary flash is set to SU-4 mode and the slave eye can see your other flash, you will be amazed at how well it all works together. And you might even feel good about how much coin you dropped on that spiffy new Nikon SB-900 speedlight. |





