Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Search results for query: *

  • Users: Ox258
  • Order by date
  1. Ox258

    programming in non-page-faults

    Ok, I have done a #include <sys/mman.h> and I did a mlockall(MCL_CURRENT | MCL_FUTURE ) to ensure that this process's current and future(stack, etc) memory is protected from page faulting. This process does a pipe to make sure it is the only version running, then does a fork() to detach from...
  2. Ox258

    programming in non-page-faults

    I just heard about something called mlock() if anyone has used this before. Tony
  3. Ox258

    programming in non-page-faults

    For some software I'm working on, I need to make sure it doesn't slow down at any time, and taking out the ability of the system to put the program threads to disk and later page fault and reload them would make it possibly too slow. This is a real-time system so this is something I must do...
  4. Ox258

    ftp using c

    I agree. The only two ways I can think of is to either write a script to deal with the logon name/password part, or create a pipe and run through it(works like system call) so you can login in that way. I think running an external cgi script is the easiest way to go. Tony
  5. Ox258

    popen and thread intereference

    Finally figured it out. All I had to do was fork() the process to detach it from the terminal. Works like a charm now :) Tony

Part and Inventory Search

Back
Top