starting pureftpd port

[Ryan Schmidt]

On Sep 19, 2009, at 13:54, Scott Haneda wrote:

>>> I can start pureftpd and it works from the command line now.   
>>> Apple has /System/Library/LaunchDaemons/ftp.plist which seems to  
>>> get the disabled key toggled around depending on how your system  
>>> preferences are set.
>>>
>>> If I want to maintain that feature, enable and disable by System  
>>> preferences, I take it I would need to alter /System/Library/ 
>>> LaunchDaemons/ftp.plist?
>>
>> I would discourage you from modifying files installed by Apple.  
>> Instead, this port should install its own launchd plist and you can  
>> manage that plist on the command line or using gui tools like lingon.
>
> Ok. Agreed. This has the problem of clicking on the FTP server in  
> Apples System Prefs Sharing pane will cause trouble.
>
> Is it worth a UI messgae to warn users, or are there any more  
> automatic or graceful ways to deal with this?
>
> I assume this is identical to the Apache ports, and just leave  
> things alone?

Yes, for the Apache ports and lighttpd and other web servers, users  
are expected to turn off Apple's Web Sharing -- or run the MacPorts  
web server on a different port. The same would apply to FTP servers or  
any other servers Apple might offer. Though I don't see an FTP server  
in my Sharing preferences -- maybe you're on Mac OS X Server?


>>> I am thinking in this case, there are so many ways to start this,  
>>> the portfile needs to just install a plist and ui_msg where it is  
>>> and how to enabled it.
>>
>> I would say the port should use the startupitem keywords like other  
>> ports do.
>
> The plist is the entire config file. So if you want port ranges,  
> umask, throttle, mysql, about 50 various configurations, there is no  
> config file.
>
> It all operates via string items to an array in launchd.
>
> What do you suggest based on that? I was going to include  
> plain.plist, ISP.plist, and a few others, with instructions on how  
> to copy and load.
>
> There are too many options, one plist can never work for everyone,  
> so I'm not sure it can be ports managed for the creation.

Oh, ok. Then I guess it should be up to the user to write and install  
the plist. The port could install a sample plist and tell the user  
about it.