FTP Won't Die

I'm running a G5 XServe. Until yesterday, I was running the normal server stuff plus the latest versions of MySQL and PHP. For FTP services, I had previously installed PureFTPd. It worked well until yesterday. I ran the 10.4.9 update, and my FTP service is now fubar. I've uninstalled PureFTP and shut down the FTP service through the Server Admin interface. But... I CAN STILL CONNECT VIA FTP! When I look at the processes running using top or Activity Monitor, I don't see anything related to FTP. Thoughts and suggestions greatly appreciated.

OK, I'm a bit more awake now. I see that when I make an SFTP connection, the sftp-server process gets launched. This seems counterintuitive, given that I have the FTP service turned off using the Server Admin tool. Does the sshd_config file need to be edited to prevent sftp connections? I'm thinking I need to comment out or delete this section:
# override default of no subsystems
Subsystem sftp /usr/libexec/sftp-server
Basically, I want to deal with the function without using blunt force blocking through the firewall ports.

Similar Messages

  • Dreamweaver ftp won't connect to host for one one site

    HI,
    have spent over 3 hours on this, and double checked
    everything, even with ISP to make sure my host address is correct.
    I can connect to the host address via other programs and ftp
    I have the same settings in dreamweaver, but it won't
    connect.
    I can connect to other sites with this same dreamweaver, and
    can create NEW connections too, but not to this one site that I can
    connect to with everything else, but dreamweaver.
    The is dreamweaver MX,
    Can anyone help?

    Adobe provides a test FTP server for these purposes. You can read about it here -
    http://helpx.adobe.com/dreamweaver/kb/troubleshoot-ftp-issues-dreamweaver-cs5.html#main_Ve rify_FTP_access
    Try setting up a connection to that server and see if you can connect.

  • Problem with processes that just won't die...

    Hi,
    first off, hullo everybody
    I'm new to Arch Linux, but I do already like it very much. I have just installed it on my workstation and it works fine, except for the following problem.
    My home directory here is mounted via NFS from a central server. My username is malte (we're using YP/NIS for central authentication) and my home dir is /WW/home/malte/
    The network file system that is mounted at boot time is /WW
    malte@bombadil $ grep nfs /etc/fstab
    quarterback:/WW    /WW           nfs       defaults               0      0
    Everything is setup at boot time automatically and all works fine so far. However, when I reboot my machine using sudo reboot, or even when cleanly logging out and using the Shutdown/Reboot button in GDM, what happens is that Arch tries to unmount the net file systems (that is, /WW in this case), but fails and outputs
    /WW: device is busy
    (or something to that effect); so it gives up, and goes on shutting down all the other services, like the network etc. At the very end, when "Unmounting all filesystems", it then again tries to unmount the net file system, which of course won't work since the network is already shut down. It tries for about a minute or so before timing out, giving up and just rebooting
    This of course is quite annoying, as I have to wait more than a minute each time I want to reboot (or I would have to press the reset button on the computer, which I really don't want to).
    So why doesn't Arch succeed in unmounting the net file system when it should? Using lsof, I have traced down the problem further:
    When I do not login as user in GDM after booting up the system, but immediately reboot again after GDM has just been started, there is no problem: /WW is unmounted properly, and my system reboots flawlessly.
    The problem is when I log in to my WM as user. Even if I log out cleanly to GDM again, there are two processes belonging to user malte that go on living and that access to /WW/home/malte, and I suppose that is why unmounting fails at reboot time, saying the device is busy.
    I have found out that (and which these processes are) by closely observing the output of watch 'lsof | grep WW' run as root on vc/1, just after I log out from my WM as user:
    root@bombadil $ lsof | grep WW # executed closely after logging out as user malte
    menu-cach 3410  malte  cwd       DIR               0,16     1536    8785908 /WW/home/malte (quarterback:/WW)
    gam_serve 5391  malte  cwd       DIR               0,16     1536    8785908 /WW/home/malte (quarterback:/WW)
    More information on those two processes:
    root@bombadil $ ps aux | grep -e gam_serv -e menu-cach
    malte     3410  0.0  0.1  41540  2680 ?        S    14:46   0:00 /usr/bin/menu-cached
    malte     5391  0.0  0.0  17444  1476 ?        S    15:38   0:00 /usr/lib/gamin/gam_server
    root      5473  0.0  0.0   9324   740 tty1     R+   15:38   0:00 grep -e gam-serv -e menu-cach
    So! In short, even after logging out, menu-cached and gam_server keep on living, and access to /WW/home/malte, and that is why when I try to reboot, Arch does not succeed in unmounting /WW, and that is why it tries to unmount it again at a later time, after networking has already been shut down, and that is why it waits for a time-out for about a minute at the end of the reboot procedure.
    In fact, gam_server only keeps on living for about 20 seconds after I logged out, then it is terminated. As for menu-cached, it goes on and on living, at least for 5 minutes, which is when I got tired of watching the output of watch 'lsof | grep WW' ;-)
    Any ideas how this could be remedied? Ideally, I'd like to be able to reboot using sudo reboot rather than by logging out and using GDM to reboot, but I guess that then there will be even more processes alive and accessing the NFS file system when already Arch tries to unmount it.
    Oh yes, maybe this is of some interest also:
    malte@bombadil $ grep DAEMONS /etc/rc.conf
    # DAEMONS
    DAEMONS=(syslog-ng network portmap nfslock @netfs ypbind sshd crond)
    Please help
    Cheers,
    Malte
    Last edited by einheitlix (2009-03-31 14:20:35)

    I have the same problem.  menu-caches doesn't die after user logs out of the session (don't have the gamin issue though).  I too am running LXDE.  When a different user logs in via gdm you'll still see the menu-cached processes for other users and I end up having to kill them as root.  I do believe this is a bug with either menu-caches and/or LXDE (or perhaps, more specifically, its session manager).  I've looked high and low through the system to figure out where menu-cached is invoked from and for any sort of associated configuration file to no avail.  I'm left with the conclusion that the invocation of menu-cached is hard-coded into start-lxde. 
    As a ugly-hack workaround you might try making a shell script like the following in /etc/gdm/PostSession/ directory:
    #!/bin/sh
    killall menu-cached
    This of course is only applicable for those running gdm as their display manager.  Also don't forget to make it executable.
    I would imagine that menu-cached not closing on user logout is very much a bug.  Or perhaps, more precisely, something that hadn't gotten put in yet.  Afterall, LXDE is still a relatively new desktop.  A good one at that so far, if you don't mind some of the missing polish that its dev haven't had a chance to add yet.
    If someone else knows a more elegant solution than that please let me, and the other LXDE users, know.
    Last edited by PingFloyd (2009-04-04 02:08:29)

  • Zombie email message won't die! $1 bounty to anyone who can solve this.

    I have a message that absolutely will not die. I've tried everything I can think of to delete it, but it keeps coming back. I've tried moving it from one mailbox to another, killing it with the delete key, killing it by cutting it (Command-X), but it lingers on. At this point, it only shows up in the index with a subject and date, but the content of the message is gone. I've tried rebuilding the mailboxes a number of times, but it always reappears. I've tried logging into my various accounts through the web interface, but it doesn't exist on the servers anywhere, it's only local as far as I can see.
    In my last attempt to get rid of it, I scanned my ENTIRE HARD DRIVE for the string of text containing the subject line using grep, and narrowed it down to a few files in the ~/Library/Mail folder, which I deleted through the Terminal using rm. I then re-opened Mail and rebuilt the mailboxes, and the email STILL appears. It will no longer let me move the message to another mailbox, however, but I can't get the damned thing to disappear.
    I will PayPal $1 to anyone who can come up with a solution that doesn't involve recreating my Mail accounts. May the game begin!

    Hello,
    Are you using an IMAP or POP account?
    Anything you do in the Terminal, Finder or some third party Mail app enhancers will very often mess up the index, which appears to be a symptom of.
    I think you should force a reindexing by deleting the Envelope Index. With IMAP or Exchange account, forcing reindexing requires removing the account folder. See:
    http://docs.info.apple.com/article.html?path=Mail/4.0/en/14019.html
    Ask any questions needed to get comfortable with doing this.
    Ernie

  • ITunes 10 starting conhost.exe and it won't die

    I updated to the latest version of iTunes about 3 weeks ago (haven't run it in over a week, due to this problem). Immediately after installing, I began seeing conhost.exe start multiple times. It took me a week to figure out which installed software was causing the issue, and narrowed it down to iTunes.
    When iTunes runs (with or without its various services started), it starts conhost.exe. Whatever it is running in that console causes every other process that starts after conhost.exe starts to never end. I had taken to killing the conhost.exe processes, but they would simply restart when the iTunes services were running.
    Basically, what this means is that when iTunes and related services were running in the background, HUNDREDS of processes that Windows starts and stops automatically would NEVER DIE. I once came home to find over 500 processes running, and before I figured out it was iTunes causing the problem, had to restart my computer every night when I got home, because the computer wouldn't respond. Each of those processes may have been small, but there were hundreds of them, taking up all available RAM.
    In case anyone is curious (which I'm sure may happen), I'm running on a self-built Core 2 Quad 2.0GHz, 8GB of RAM, Windows 7 Ultimate x64, with somewhere near 3TB of storage space (approximately 60% of which is available). There are no current hardware issues, all drivers are up to date, and air flow through the case is taken care of by 8 case fans. Keeps my processor temps right around 100F (which is a lot cooler than they were over the summer).
    The iTunes.exe version information says it is version 10.0.0.68. I know there's a 10.0.1 out now, but can't find out whether or not it resolves this issue.
    Anyone have any ideas? This may be specific to Windows 7 x64; I haven't been able to find any solutions in my searching, both here and on Google.
    Thanks.

    Empty/corrupt library after upgrade/crash
    Hopefully it's not been too long since you last upgraded iTunes, in fact if you get an empty/incomplete library immediately after upgrading then with the following steps you shouldn't lose a thing or need to do any further housekeeping. In the Previous iTunes Libraries folder should be a number of dated iTunes Library files. Take the most recent of these and copy it into the iTunes folder. Rename iTunes Library.itl as iTunes Library (Corrupt).itl and then rename the restored file as iTunes Library.itl. Start iTunes. Should all be good, bar any recent additions to or deletions from your library.
    See iTunes Folder Watch for a tool to catch up with any changes since the backup file was created.
    When you get it all working make a backup!
    tt2

  • The Pop-up That Won't Die In Pages Tracking

    Pages version 4.1 (923) running on Lion, OSX 10.7
    When you turn on Tracking, an annoying translucent post-it pops up—no matter where you put your cursor. It tells you the last thing you did in the document, and when you did it—like that's something you need to know.
    And it won't go away until you click someplace else in the document.
    AND there's no way to turn the feature off. Really, I looked everywhere in preferences, and an Apple Pages specialist confirmed that on the phone.
    I swear, it's as bad as the paperclip in MS Word.
    OH! And on Lion -- the damned thing stays on the screen when you switch apps. I'm looking at one right now at the bottom of the screen, while I'm in Safari. And it MOVES—now it's on top of this message's menu bar. It appears and disappears. To get rid of it, I'd have to switch pack to Pages and click somewhere in the doc. It's like a villain in Doctor Who.
    Since there's no way to turn it off in the program, that leaves the terminal—which I've never used but am willing to brave if someone would be so kind as to tell me what the frak to do and how to do it?
    Pretty please?
    Or is there someone smart enough write an Applescript or patch?? I'm dyin' here.
    Thank you in advance,
    outlaw

    As far as I know, the local menu entitled "Bulles de suvi" in French isn't deeply buried !
    Check the item "Hide All" and, what a wonderful surprise, the post-its will no longer pop.
    To Peter's attention, it's not a system feature, just a Pages's documented one
    Yvan KOENIG (VALLAURIS, France) dimanche 7 août 2011 16:59:24
    iMac 21”5, i7, 2.8 GHz, 4 Gbytes, 1 Tbytes, mac OS X 10.6.8 and 10.7.0
    My iDisk is : <http://public.me.com/koenigyvan>
    Please : Search for questions similar to your own before submitting them to the community
    To be the AW6 successor, iWork MUST integrate a TRUE DB, not a list organizer !

  • Ken burns effect won't die

    I want to globally turn off the Ken Burns effect for my 722 slides in my iMove slide show. I have clicked on Project Properties, Timing, Fit in Frame, apply to all.
    But still it won't go away. I really don't want to do one at a time. What else can I do?

    Click on one of the thumbnail images in the project timeline, then select "Edit > Select All" from the menu. All clips in the project will now be highlighted with a yellow border.
    Now click on the small gear icon on one of the images. From the drop-down menu select "Cropping & Rotation". (Alternatively, click on the Crop, Rotate & Ken Burns tool in the centre toolbar - or simply press the C key on the keyboard).
    In the Viewer, select Fit (in the top left corner). All clips will now be changed to Fit.
    It's best when starting a new project to choose your preference from "File > Project Properties", then make a selection for the item "Initial Photo Placement". iMovie's default is Ken Burns (as you've discovered).
    John

  • FTP won't connect Get multiple daemons

    I had the problem where no one could connect with any password in FTP. I replaced the /Library/FTPServer/Configuration/ftpaccess file and fixed the bad password problem.
    For a few minutes I could connect. Now I cannot. When I try to connect I get:
    ++++
    ftp server1
    Connected to server1.<ourDomain>.com.
    (Here long wait)
    421 Service not available, remote server timed out. Connection closed
    +++++
    On the server itself I find instances of the daemon where I had tried to connect before:
    ++++++
    admin$ ps -ax | grep xftp
    411 ?? R 2:07.21 xftpd -a
    440 ?? R 1:01.14 xftpd -a
    441 ?? R 1:00.91 xftpd -a
    463 ?? R 0:50.93 xftpd -a
    477 ?? R 0:32.96 xftpd -a
    478 ?? R 0:32.22 xftpd -a
    481 ?? R 0:22.42 xftpd -a
    482 ?? R 0:22.22 xftpd -a
    491 ?? R 0:20.26 xftpd -a
    494 ?? R 0:08.76 xftpd -a
    495 ?? R 0:08.65 xftpd -a
    510 p2 U+ 0:00.00 grep xftp
    Any help would be appreciated.

    In addition to this, When ever I try to connect, I start an Xftp daemon that EATS cpu time.
    The SAMPLE data is below.
    Thanks
    Kirk
    +++++++TOP+++++++++
    Processes: 125 total, 5 running, 1 stuck, 119 sleeping... 390 threads 14:51:53
    Load Avg: 2.50, 2.26, 1.78 CPU usage: 30.1% user, 69.9% sys, 0.0% idle
    SharedLibs: num = 188, resident = 41.5M code, 4.63M data, 10.5M LinkEdit
    MemRegions: num = 13841, resident = 313M + 17.5M private, 130M shared
    PhysMem: 159M wired, 169M active, 389M inactive, 718M used, 1.30G free
    VM: 7.11G + 107M 112124(0) pageins, 0(0) pageouts
    PID COMMAND %CPU TIME #TH #PRTS #MREGS RPRVT RSHRD RSIZE VSIZE
    28709 top 15.0% 0:02.16 1 19 22 488K 504K 936K 26.9M
    28708 pop3d 0.0% 0:00.06 1 18 80 472K 2.20M 1.90M 48.7M
    28707 imapd 0.0% 0:00.13 1 25 86 684K 2.71M 2.41M 49.4M
    28596 xftpd 70.9% 5:20.61 1 17 30 200K 612K 672K 26.8M
    28565 smtpd 0.0% 0:00.07 1 16 76 452K 1.57M 1.68M 29.3M
    28557 imapd 0.0% 0:00.10 1 25 86 688K 2.71M 2.37M 49.4M
    28490 trivial-re 0.0% 0:00.03 1 16 20 200K 568K 708K 26.7M
    28361 imapd 0.0% 0:00.26 1 25 91 672K 2.83M 2.41M 49.7M
    28360 imapd 0.0% 0:00.13 1 25 86 668K 2.72M 2.39M 49.4M
    +++++++++++++Output+++++++
    Analysis of sampling pid 28596 every 10.000000 milliseconds
    Call graph:
    849 Thread_011f
    849 0x21c8
    849 0x2320
    849 0xca30
    849 0x1ca7c
    849 0x1c4f4
    633 0x1b030
    575 lstat
    575 lstat
    57 0x1b030
    1 dyldstublstat
    1 dyldstublstat
    150 0x1b064
    133 readlink
    133 readlink
    16 0x1b064
    1 dyldstubreadlink
    1 dyldstubreadlink
    12 0x1b010
    7 strcat
    7 strcat
    5 dyldstubstrcat
    5 dyldstubstrcat
    7 0x1af94
    5 strchr
    5 strchr
    2 dyldstubstrchr
    2 dyldstubstrchr
    7 0x1afcc
    4 strcpy
    4 strcpy
    3 dyldstubstrcpy
    3 dyldstubstrcpy
    6 0x1b0ec
    4 strcpy
    4 strcpy
    2 dyldstubstrcpy
    2 dyldstubstrcpy
    5 0x1aeec
    3 bcmp
    3 bcmp
    2 dyldstubmemcmp
    2 dyldstubmemcmp
    5 0x1b024
    3 strcat
    3 strcat
    2 dyldstubstrcat
    2 dyldstubstrcat
    3 0x1afa4
    3 strlen
    3 strlen
    3 0x1aff4
    3 0x1aff4
    3 0x1b038
    3 0x1b038
    2 0x1af10
    2 dyldstubmemcmp
    2 dyldstubmemcmp
    2 0x1af34
    2 dyldstubmemcmp
    2 dyldstubmemcmp
    2 0x1afe8
    2 0x1afe8
    2 0x1b088
    2 0x1b088
    2 0x1b0c4
    2 strcpy
    2 strcpy
    1 0x1afc0
    1 0x1afc0
    1 0x1afe4
    1 0x1afe4
    1 0x1b044
    1 0x1b044
    1 0x1b048
    1 0x1b048
    1 0x1b074
    1 0x1b074
    Total number in stack (recursive counted multiple, when >=5):
    Sort by top of stack, same collapsed (when >= 5):
    lstat 575
    readlink 133
    0x1b030 57
    0x1b064 16
    strcat 10
    strcpy 10
    dyldstubstrcat 7
    dyldstubmemcmp 6
    dyldstubstrcpy 5
    strchr 5

  • Firefox process won't die

    When I quit/close Firefox, wait 1 minute, then reopen Firefox, Firefox does not open...it just hangs.
    When looking in my Task Manager, there are two firefox.exe processes running. Killing the process via the Task Manager is required to get Firefox to open/run again.

    I'm quite familiar with the issue you've proposed via this KB article. My issue, though, is quite different. I don't get the annoying "Firefox is already running, but is not responding. To open a new window, you must first close the existing Firefox process, or restart your system.." alert box.
    Further, with the known issue, the firefox process does eventually die. With this new issue, the firefox process never dies and appears orphaned.
    Keep in mind this only started occurring after I upgraded to version 3.6.9 two days ago. There is no doubt in my mind something is broken in the newest build.
    As a developer, I like adhering an important and well-known principle in the software development world when I build and maintain stuff: if it ain't broke, don't fix it. Sometimes I wonder/question if Mozilla developers hold the same conviction, given numerous new issues that make it into every new build of Firefox.
    This also brings up another subject: does anyone do QA anymore? I like to test my stuff before letting others use it. It's extremely important to make sure your stuff is solid, before letting others use it. Cross your T's and dot your I's, for heaven's sake!

  • FTP won't disconnect on idle

    Let me start by saying when I initially connect to an FTP
    server, I have no problem uploading or downloading files.
    However, regardless of what value I place in the "Disconnect
    after X Minutes idle" DW never disconnects, but sits there showing
    a valid connection after the FTP server has long since dropped the
    connection. This becomes a pain when I try to upload another file
    and DW has to time out, then try to re-establish a connection
    (which usually fails), times out again, then gives me an error msg.
    If I manually click the button, I then have to manually cancel the
    "background file activity" or wait for another time out. This is
    ongoing - I've been trying to manually disconnect every time I
    upload a file, but this is a hassle which I shouldn't have to do.
    This occurs on all sites and different servers, too.
    I'm using DW CS3 on Vista, FWIW. Thanks for your
    consideration of my issue.

    When I brought this up with tech support, they said DW does
    not automatically disconnect; that if I wanted this behavior I
    should add that as a feature request for the program! This is
    despite the fact the 'preferences' dialog implies this and the help
    files say it. Sheesh.

  • Eclipse won't die

    I have been having this problem ever since jdk 1_5_0_03, I now use 1_5_0_08, Eclipse is 3.2.1-1. I have a few plugins installed, but the problem is reproducible with a fresh Eclipse install, so I don't think this is the issue.
    The problem itself is that when I try to close Eclipse it doesn't die -- 2 processes are left sleeping on the system, the workspace remains locked, but the worst part is that somehow they hook to the keyboard, and do not let any key events to reach X -- I have no keyboard untill the processes are manually killed (luckily, Ctrl+Alt+F1 works).
    Running eclipse with strace -f, I get the following before the processes hang:
    Process 7703 detached
    [pid  7693] <futex> )       = 1
    [pid  7693] gettimeofday({1160597907, 593421}, NULL) = 0
    [pid  7693] futex(0x809975c, 0x5 /* FUTEX_??? */, 1 <unfinished>
    [pid  7695] <futex> )       = 0
    [pid  7693] <futex> )       = 1
    [pid  7695] futex(0x805beb0, FUTEX_WAIT, 2, NULL <unfinished>
    [pid  7693] futex(0x805beb0, FUTEX_WAKE, 1 <unfinished>
    [pid  7695] <futex> )       = -1 EAGAIN (Resource temporarily unavailable)
    [pid  7693] <futex> )       = 0
    [pid  7695] futex(0x805beb0, FUTEX_WAKE, 1 <unfinished>
    [pid  7693] futex(0x8324f9c, FUTEX_WAIT, 101, NULL <unfinished>
    [pid  7695] <futex> )       = 0
    [pid  7695] gettimeofday({1160597907, 593738}, NULL) = 0
    [pid  7695] gettimeofday({1160597907, 593787}, NULL) = 0
    [pid  7695] mprotect(0xb7f2d000, 4096, PROT_READ) = 0
    [pid  7695] mprotect(0xb7f2d000, 4096, PROT_READ|PROT_WRITE|PROT_EXEC) = 0
    [pid  7695] mprotect(0xb7f2e000, 4096, PROT_NONE) = 0
    [pid  7695] gettimeofday({1160597907, 594018}, NULL) = 0
    [pid  7695] gettimeofday({1160597907, 594100}, NULL) = 0
    [pid  7695] gettimeofday({1160597907, 596337}, NULL) = 0
    [pid  7695] unlink("/tmp/hsperfdata_kenny/7693") = 0
    [pid  7695] pipe([10, 12])              = 0
    [pid  7695] pipe([26, 27])              = 0
    [pid  7695] clone(Process 7978 attached
    child_stack=0xb1e844d4, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tidptr=0xb1e84be8, {entry_number:6, base_addr:0xb1e84ba0, limit:1048575, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0, useable:1}, child_tidptr=0xb1e84be8) = 7978
    [pid  7695] writev(23, [{"GIOP1212341", 12}, {"22036F262334e26030H"..., 412}], 2) = 424
    [pid  7695] futex(0x8b3b9cc, FUTEX_WAIT, 1, NULL <unfinished>
    [pid  7700] <futex> )       = 0
    [pid  7700] futex(0x805be30, FUTEX_WAIT, 2, NULL <unfinished>
    [pid  7978] poll([{fd=10, events=POLLIN}, {fd=25, events=POLLIN|POLLPRI, revents=POLLIN}, {fd=23, events=POLLIN|POLLPRI}, {fd=22, events=POLLIN|POLLPRI}, {fd=21, events=POLLIN|POLLPRI}, {fd=20, events=POLLIN|POLLPRI}, {fd=26, events=POLLIN|POLLPRI}], 7, -1) = 1
    [pid  7978] read(25, "GIOP121T", 12) = 12
    [pid  7978] read(25, "|317277334216f26420"..., 84) = 84
    [pid  7978] write(19, "A", 1)           = 1
    [pid  7978] poll(
    These are the processes themselves (partial output from `ps axjf`):
    kenny     7689  0.7  0.1   1696   720 pts/2    S+   23:10   0:13 strace -f ./eclipse
    kenny     7690  0.0  0.2  12580  1816 pts/2    T+   23:10   0:00 ./eclipse
    kenny     7693  1.6 11.6 499124 82916 pts/2    Sl+  23:10   0:30 /opt/java/bin/java -Xms40m -Xmx256m -jar /opt/eclipse/./startup.jar -os linux -ws gtk -arch x86 -launcher /opt/eclipse/./eclipse -name Eclipse -showsplash 600 -exitdata 3f0018 -vm /opt/java/bin/java -vmargs -Xms40m -Xmx256m -jar /opt/eclipse/./startup.jar
    I would really appreciate any help or suggestions.

    Try this?
    java -Xms256m -Xmx320m -XX:PermSize=64m -XX:MaxPermSize=128m -jar /usr/local/lib/eclipse/startup.jar -os linux -ws gtk -arch x86 -launcher /usr/local/lib/eclipse/eclipse -name Eclipse -showsplash 600 -exitdata 4aeb003f -vm /opt/java/jre/bin/java -vmargs -jar /usr/local/lib/eclipse/startup.jar

  • FTP Won't connect. Any ideas?

    I have a client that is trying to switch from FrontPage to Adobe Muse. However they can not get the FTP to work. I downloaded Muse and tired it also and I can't get it to work either. This is the message the FTP screen gives me.
    However when I log into the server it appears the connection username password etc all work fine. As you can see here by the FTP server interface
    So my question is why can't Muse seem to open a data connection when the username and password are fine? Also I tried the same username and password and host info in FileZilla client and of course it works fine.

    Hi,
    Do you support EPSV? When you tried FileZilla client, was it using EPSV?
    Are there any server-side logs?
    Thanks,
    Abhishek

  • IWeb integrated ftp won't connect. Settings confirmed via standard ftp client

    I am nable to ftp via the iWeb integrated ftp interface. I have tested the settings via a standard ftp client without issue.
    Any ideas?
    Thanks! Joe

    iWeb is kind of unusual in that it publishes a folder containing the website files and an external index.html that opens the home page. There's also a copy of this index.html file inside the folder.
    This arrangement is to suit publishing to the Apple server - MobileMe - and is kind of illogical when publishing else where.
    Uploading using the iWeb built in FTP means that the URL has the folder name in the path...
    http://www.domain-name.com/Site-Name/Page-Name.html
    To avoid this, the site needs to be published to a local folder using the second method on the page I referred to above and the files inside the folder uploaded to the root on the server....
    http://www.iwebformusicians.com/iWeb/URLs-Favicons.html

  • Ftp won't connect

    GREetings All,
    I am having trouble with dreamweaver's ftp setup. I have allowed through the firewall and changed username an password but when I test it it still doesn't connect it says local firewall blocked ftp data.
    How do I fix this problem?

    Enable passive FTP and try again, please.

  • Dreamweaver CS3 ftp won't connect

    Very unusual ftp problem: Server is MS IIS. I have multiple
    Dreamweaver sites defined for this server. Been using them for
    years. All sites connect fine except one. The one initially worked.
    For the one problem site, clicking the Test button in Remote Info
    tab connects just fine. Clicking the Connect button in Files will
    time out every time. Using WSFTP to the same site and folder works
    just fine. The only difference between this site and the ones that
    work is the folder name. They even share the same parent folder.
    ftp connection parameters are the same. How can this be?

    I solved it myself. It turned out to be a corrupt site
    definition in Dreamweaver. By deleting the site, then recreating
    it, everything works as it should.

Maybe you are looking for