Find the answer to your Linux question:
Results 1 to 3 of 3
Dear all, I've got a problem in /proc inside a directory pertinent to a PID, for example /proc/44444 i've got a missing link, exe is actually poiniting to nowhere. When ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Mar 2007
    Posts
    2

    replacing missing link in /proc


    Dear all,
    I've got a problem
    in /proc inside a directory pertinent to a PID, for example /proc/44444
    i've got a missing link, exe is actually poiniting to nowhere.

    When I launch top, I can see the process 44444 running but any attempt to kill this pid has failed.

    I also tried to replace the missing link to the correct path, but the system does not allow me to remove the exe entry before recreating it.

    What can I do without obviously reboot the system ?

    Thanks a lot


    Andrea

  2. #2
    Linux Newbie dilbert's Avatar
    Join Date
    Sep 2006
    Location
    Yorkshire, GB
    Posts
    237
    Does it mean if you reboot the system, then you would get that missing link back?

    First, the proc file system and portions of it have to be mounted somewhere at configuaration, and secondly, the drivers populate this file system.

    If you could rmmod and insmod the particular driver, maybe that repairs the missing link.

    Question is also, who takes off that missing link. Probably an error in that driver that writes into that part of the proc file system.
    Bus Error: Passengers dumped. Hech gap yo'q.

  3. #3
    Just Joined!
    Join Date
    Mar 2007
    Posts
    2

    replacing missing link in /proc

    Thanks for Your answer,
    I'll try to provide more information,
    an application has been lauched via shell,
    usually when this happen a pid director will be created in /proc, the exe soft link points to the excutable launched via shell command (or that is what I think this should be). In my case, various istances of this application were launched, all were killed via kill -9 except this one. The only anomaly I've found concerning this latter case was the unresolved link in the proc dir. So I guessed this could be the problem.

    We are using SLES 9 SP3
    (kernel Linux t 2.6.5-7.244-smp #1 SMP Mon Dec 12 18:32:25 UTC 2005 x86_64 x86_64 x86_64 GNU/Linux )

    I'll expect that after a reboot this problem will not reappear unless the application will be relaunched via shell (but please remember all of the other istances of this application were successfully killed).


    Thanks a lot for Your kind interest


    Andrea

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •