system("shutdown -s -t 10");
vs
ExitWindowsEx(EWX_POWEROFF, SHTDN_REASON_MAJOR_OTHER);
Which is better? and why?
system("shutdown -s -t 10");
vs
ExitWindowsEx(EWX_POWEROFF, SHTDN_REASON_MAJOR_OTHER);
Which is better? and why?
The later, obviously. It's more secure, and it's faster.
Originally Posted by Adak
Wow.. an user application can shut down Windows just like that ?....no complains from the operating system or other users that might be logged in ?
Of course they can, with proper permissions, of course.
They have to request permission to be able to shut down the system first. If that requires admin privileges or not, I don't know.
@manasij7479 I'm not sure, but i'll assume SHTDN_REASON_MAJOR_OTHER will give some kind of message, because system(); give a message. Although i haven't tired it yet so i wouldn't know.
I'm having trouble running exitwindowsEx. It seems more complicated than system();. Could someone figure out what is wrong with the code below? I can't seem to complie the error();.
Code:HANDLE hToken; TOKEN_PRIVILEGES tkp; // Get a token for this process. if (!OpenProcessToken(GetCurrentProcess(), TOKEN_ADJUST_PRIVILEGES | TOKEN_QUERY, &hToken)) error("OpenProcessToken"); // Get the LUID for the shutdown privilege. LookupPrivilegeValue(NULL, SE_SHUTDOWN_NAME, &tkp.Privileges[0].Luid); tkp.PrivilegeCount = 1; // one privilege to set tkp.Privileges[0].Attributes = SE_PRIVILEGE_ENABLED; // Get the shutdown privilege for this process. AdjustTokenPrivileges(hToken, FALSE, &tkp, 0, (PTOKEN_PRIVILEGES)NULL, 0); // Cannot test the return value of AdjustTokenPrivileges. if (GetLastError() != ERROR_SUCCESS) error("AdjustTokenPrivileges"); // Shut down the system and force all applications to close. if (!ExitWindowsEx(EWX_REBOOT | EWX_FORCE, 0))
No, it won't. This is an API; not an application. APIs typically don't display messages. That is the application's job.
shutdown is an application, while ExitWindowsEx is not.
You should post your query in the Windows forum.
Moved
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
"Shutdown", "halt", "reboot", etc, are user applications. On *nix systems this is done via kill(1,...).
C programming resources:
GNU C Function and Macro Index -- glibc reference manual
The C Book -- nice online learner guide
Current ISO draft standard
CCAN -- new CPAN like open source library repository
3 (different) GNU debugger tutorials: #1 -- #2 -- #3
cpwiki -- our wiki on sourceforge
ok nvm, i figured it out. Cheers
Share your solution with the rest of the world, that others may benefit from this topic and your problem!
