Error Unable To Open /dev/log Solaris
last lines I get are ... socket(PF_INET, SOCK_STREAM, IPPROTO_TCP) = 3 ioctl(3, SNDCTL_TMR_TIMEBASE or TCGETS, 0xbfa99308) = -1 EINVAL (Inval +id argument) _llseek(3, 0, 0xbfa99350, SEEK_CUR) = -1 ESPIPE (Illegal seek) ioctl(3, SNDCTL_TMR_TIMEBASE or TCGETS, 0xbfa99308) = -1 EINVAL (Inval +id argument) _llseek(3, 0, 0xbfa99350, SEEK_CUR) = -1 ESPIPE (Illegal seek) fcntl64(3, F_SETFD, FD_CLOEXEC) = 0 setsockopt(3, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0 bind(3, {sa_family=AF_INET, sin_port=htons(7070), sin_addr=inet_addr(" +0.0.0.0")}, 16) = 0 listen(3, 1) = 0 accept(3, [download] It could be one of fcntl, setsockopt, bind or listen failing (all may potentially set EBADF). Then, depending on which one it is, look in the respective man page. If you're lucky, you might find something resembling an explanation... Comment on Re: Could not create socket: Bad file numberSelect or Download Code Replies are listed 'Best First'. Re^2: Could not create socket: Bad file number by perlofwisdom (Pilgrim) on Aug 30, 2007 at 23:27UTC Thanks for the "strace" suggestion. I've never used it before, and there's no man-page for it, so I probably got the syntax wrong. Here's what I tried: -> strace perl receive.pl ERROR: unable to open /dev/log [download] I also tried a 'set -x', but that returned the same results I was getting before, no detail.[reply][d/l] Re^3: Could not create socket: Bad file number by almut (Canon) on Aug 30, 2007 at 23:44UTC Which platform are you on? The strace I was referring to is a Linux tool -- on some other unixes, the program named strace is an entirely different tool... [ Update: actually, that's exactly the error message you get when you try to run strace (STREAMS trace) on Solaris as a regular user (because the device that /dev/log points to is owned by root:sys). On HP-UX and AIX I'm getting different error messages -- but YMMV. So I supppose what you want is truss (usage for simple things is essentially the same as strace under Linux). ] A couple of weeks ago, I posted a list of corresponding tools for other platforms... (if the respective tool you want is not installed already, you should be able to download it from the net). (BTW, you called it correctly.) [reply][d/l][select] In Section Seekers of Perl Wisdom
Solaris 8/SPARC darcs 1.0.2 Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] On 2005-02-14, Jason Dagit
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies http://superuser.com/questions/222901/can-i-find-out-which-files-are-open-in-an-emacs-instance-running-on-remote-works of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Super User Questions Tags Users Badges Unanswered Ask Question _ Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute: Sign up Here's how it works: Anybody can error unable ask a question Anybody can answer The best answers are voted up and rise to the top Can I find out which files are open in an Emacs instance running on remote workstation? up vote 1 down vote favorite I have several instances of Emacs (v21.2.1) running on a remote workstation, one of which I would like to kill via ssh. I can error unable to get the PIDs of each instance (using pgrep emacs, say) while ssh'd into the workstation, but I don't know how to determine which of those processes has a particular file open. lsof doesn't return any information that's obviously useful, presumably because Emacs doesn't keep the files open while they are being edited in a buffer. Maybe it's possible to export the existing Emacs windows to my current location, but I don't know how I would go about that. Am I foolish in thinking this is even possible? ssh emacs share|improve this question asked Dec 16 '10 at 23:05 Deditos 629514 add a comment| 2 Answers 2 active oldest votes up vote 1 down vote accepted Use strace to see what files it has open (it does keep things open, or at least is often checking on the files). This should give you a list of everything that the process is looking at, obviously you'll have to parse it somewhat and filter out duplicates (and substitute the proper pid): strace -p1337 -e trace=file It generates output like this: unlink("/tmp/emacsBYJwbf") = 0 stat("/home/tjackson/.jabber-avatars", {st_mode=S_IFDIR|0755, st_size=16384, ...}) = 0 stat("/home/tjackson/.jabber-avatars/e7e63a04ac20783855