526 reputation
517
bio website
location /dev/null
age
visits member for 1 year, 9 months
seen Jan 21 at 11:19

Well, I like penguins. xD


Mar
30
awarded  Notable Question
Feb
10
awarded  Popular Question
Feb
3
awarded  Revival
Jan
15
awarded  Revival
Jan
3
revised 12.04: Kernel Update - Stopping System Runlevel V Compatibility
Improved Format
Jan
3
suggested suggested edit on 12.04: Kernel Update - Stopping System Runlevel V Compatibility
Jan
3
comment Logout scripts: not completed on shutdown, reboot
Its Okay. Least I learnt a lot while researching for the same. Have fun.
Jan
3
comment Logout scripts: not completed on shutdown, reboot
@falconer, Hope everything is good. !
Jan
3
revised Logout scripts: not completed on shutdown, reboot
added 249 characters in body
Jan
3
revised Linux Anti-Virus
improved format
Jan
3
suggested suggested edit on Linux Anti-Virus
Jan
3
revised Security measures for Thunderbird and Pidgin
improved formatting
Jan
3
suggested suggested edit on Security measures for Thunderbird and Pidgin
Jan
3
comment The CPU has been disabled by the guest operating system. You will need to power off or reset the virtual machine at this point
Thats real strange coz It worked perfectly fine for another user facing same problem as you. ?? Read here. (stackoverflow.com/questions/17312295/…)
Jan
3
revised How to scan my flash drives for Windows viruses while on Linux? (Not ClamAV)
added 13 characters in body
Jan
3
comment Logout scripts: not completed on shutdown, reboot
@falconer Kindly shoot if anything else remains coz bounty is ending in just T- 11 hours. :)
Jan
3
comment Logout scripts: not completed on shutdown, reboot
I even tried scripts sorry they wont help, parsing logs wont help either, only way you can do that is to using sudo and walling off access to shutdown/reboot. Letting you know,how to do that, well will be a whole lot another answer. Hope that helps.
Jan
3
comment Logout scripts: not completed on shutdown, reboot
@falconer and @OP, So I had a hearty discussion regarding the solution to knowing username who initiated shutdown here(unix.stackexchange.com/questions/107501/…). Much to my wonders, You can't know user because there is a interface that catches the signal to shutdown/reboot and then triggers it. This process runs as root so you'll never see a username that way. Using sudo and walling off access to shutdown/reboot is just how sysadmins do this.-from a person who managed a fortune 500 company infrastructure.
Jan
3
comment Hostapd serves all webpages to Windows 7 client, not so XP or Android
I love this guy :P Solved, Hmph ! Not solved :P Just for fun :D
Jan
3
comment Logout scripts: not completed on shutdown, reboot
@falconer I guess you are true, parsing system log files wont be any help as it isn't the user who runs shutdown but some system process. Also i tried doing the same, I initiated a shutdown at 10:10:34 and started my system at 10:11:16, no username is there. Look here : pastebin.com/5g6RpmuM