A Job for Aperture?

Since I bought Aperture (now using 2.0) primarily for processing photos I take (mostly in RAW), I have not spent much time thinking about more general usage. Now I am helping, along with one other fellow, to edit about 1200 photos (JPEG) of historic family Bible pages, for genealogy purposes. Our job is to crop for later printing, and also to provide enhancements that will aid in transcription, and not simply printing of an image. Since he only has PS 7 on a PC, I think I would have greater flexibility with my software and equipment.
From past experience with old photos, more so than modern, I know a lot of tricks with Photoshop and Graphic Converter to make text in the images more readable. But that normally involves only a few images at a time -- not 1200, or even 600 if we divide up evenly.
With PS CS3, you can now open JPEGs as RAW and have the same adjustment sliders, for the most part, as with those that are in RAW. Aperture presents similar controls.
Objective is to have more than one version (different adjustments) of the photo of each page to maximize deciphering of aged handwriting, to then provide to those who will transcribe. Aperture would have some advantages in managing multiple versions, I would expect, but is there a significant work flow with Aperture vs what I would normally have done with Photoshop, one photo at a time? If so, how do I reap the most benefit?
Ernie

For versioning, Aperture or LightRoom (which I'll ignore from here on) beat Photoshop hands down. Speed wise also opening and working on that many photos, Aperture with its versions is the answer. You could have three versions side by side for comparison very quickly, and make the exact same crop to each version. Finally you will not have 3 separate images for each image until final output. After giving images to the printer you can just delete them as you could always reproduce them in a heartbeat. Organization is also much simpler as you will not have all those hi-res space robbing copies of the same image all over the place.

Similar Messages

  • A Good Reference for Aperture, Versions, File Names, Changing & Moving

    I was wondering if there is a consensus on a good reference for understanding how Aperture handles files?
    Versions and file names.
    How do you change them in Aperture?
    What happens if you change them in Finder?
    Do I need versions? (can't I just us file names?)
    What about moving the masters, or changing where there are located at in Finder?
    Can I do that in Aperture?
    Can I only do that in Finder?
    Should I never do that in Finder?
    The reason I'm looking for a good reference is because I haven't found one. The user guide (or manual) that comes with Aperture doesn't help with these issues. Search file name and nothing comes back.
    I did get a copy Apple Pro Training Series book for Aperture 3. But I don't think it does a good job explaining how Aperture's file system works, especially in relation to Finder.
    Rather than fill this forum with endless questions (which could be answered by reading the manual and using it the software) I'd like to get a better understanding, from a good source.
    I've only used iPhoto for Mobile Publishing, ATV and now Photo Stream. I don't use it to organize my decades of photos. I don't like having all my photos inside a managed database, which I don't have to do with Aperture. I never understood why you'd want to change the name of a photo in iPhoto, when it never changes the file name. If you send it to someone, after you changed it's name, the other person gets the photo with the original (still in Finder) file name.
    Thanks.

    I never understood why you'd want to change the name of a photo in iPhoto, when it never changes the file name.
    This may help or not but here goes.
    There's a distinction to be made between files and the data they contain. The example I use is as follows: In my iTunes Library I have a file called 'Let_it_Be_The_Beatles.mp3'. So what is that, exactly? It's not the song. The Beatles never wrote an mp3. They wrote a tune, some lyrics, recorded it and a copy of that recording is stored in the mp3 file. The file is just a container for the recording. That container is designed in a specific way attuned to the characteristics and requirements of the data. Hence, mp3.
    Similarly that Jpeg / tiff/ raw/ whatever is not your photo, it's a container designed to hold that kind of data. And along with that data comes opportunities: Metadata, for a start. Exif and IPTC contain vast amounts of information - some it very basic, like the date and time the shot was taken - some of it quite complex, like a lot of details of the settings used in the camera.
    Aperture, iPhoto et al are all about the data and not the file. Import the file and forget about it. Process the image - crop it, fix red eye, run it through the whole gamut of tools in the App and the file never changes at all. Create multiple versions of the image. But there's still only one file. Name it. You name the photo - and that is an entry in the Exif or IPTC. The name of the photo has nothing to do with the name of the file. Because the file is just the tin for the beans.
    Even when you export, unless you specifically choose to export the Master, you are exporting the processed Photo into a different container - that's why you can export Raw as Jpeg, or Jpeg as Tiff. Because the process of export just puts the image into a new container.
    Basically, if you want to manage files you need to use a File Manager. But you're using a Photo manager and expecting it to behave like a file manager.
    And, of course, apps like Aperture and iPhoto have the option to use the Title of the photo as filename on export to the new file.
    Does that muddy the waters?

  • Is there a text tool for Aperture?

    I would like to print a photo from Aperture or iPhoto with a text title someplace inside the photo, to use as a cover for a DVD. I searched for any text tools but none available (you can write text when printing a book which is not what I need). I solved my problem by using HeliosPaint but was wondering why Aperture does not have it available.

    I solved my problem by using HeliosPaint but was wondering why Aperture does not have it available.
    Because that's not what Aperture is meant for. That said, you can use the book tool to create this type of layout and export the page as a pdf. You can also use the print dialog to add text and print to pdf. There's also the free BorderFX plugin (here I go again) that can do the job.
    But really, the best thing is always to use the right tool for the job. Aperture has minimal design capabilities simply because it's not a design app.

  • Job for httpd.service failed. See 'systemctl status httpd.service' and

    Hello,
    I am the problem. I change "/etc/httpd/conf/httpd.conf" to install php5 on apache.
    sudo systemctl start httpd
    Job for httpd.service failed. See 'systemctl status httpd.service' and 'journalctl -xn' for details.
    systemctl status httpd.service
    ● httpd.service - Apache Web Server
    Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled)
    Active: failed (Result: exit-code) since lun. 2014-08-25 12:19:31 CEST; 1min 18s ago
    Process: 2208 ExecStop=/usr/bin/apachectl graceful-stop (code=exited, status=1/FAILURE)
    Process: 2433 ExecStart=/usr/bin/apachectl start (code=exited, status=1/FAILURE)
    Main PID: 2060 (code=exited, status=0/SUCCESS)
    août 25 12:19:31 creaprog apachectl[2433]: httpd: Syntax error on line 66 o...y
    août 25 12:19:31 creaprog systemd[1]: httpd.service: control process exite...=1
    août 25 12:19:31 creaprog systemd[1]: Failed to start Apache Web Server.
    août 25 12:19:31 creaprog systemd[1]: Unit httpd.service entered failed state.
    Hint: Some lines were ellipsized, use -l to show in full.
    cat /etc/httpd/conf/httpd.conf
    # This is the main Apache HTTP server configuration file. It contains the
    # configuration directives that give the server its instructions.
    # See <URL:http://httpd.apache.org/docs/2.4/> for detailed information.
    # In particular, see
    # <URL:http://httpd.apache.org/docs/2.4/mod/directives.html>
    # for a discussion of each configuration directive.
    # Do NOT simply read the instructions in here without understanding
    # what they do. They're here only as hints or reminders. If you are unsure
    # consult the online docs. You have been warned.
    # Configuration and logfile names: If the filenames you specify for many
    # of the server's control files begin with "/" (or "drive:/" for Win32), the
    # server will use that explicit path. If the filenames do *not* begin
    # with "/", the value of ServerRoot is prepended -- so "logs/access_log"
    # with ServerRoot set to "/usr/local/apache2" will be interpreted by the
    # server as "/usr/local/apache2/logs/access_log", whereas "/logs/access_log"
    # will be interpreted as '/logs/access_log'.
    # ServerRoot: The top of the directory tree under which the server's
    # configuration, error, and log files are kept.
    # Do not add a slash at the end of the directory path. If you point
    # ServerRoot at a non-local disk, be sure to specify a local disk on the
    # Mutex directive, if file-based mutexes are used. If you wish to share the
    # same ServerRoot for multiple httpd daemons, you will need to change at
    # least PidFile.
    ServerRoot "/srv/http"
    # Mutex: Allows you to set the mutex mechanism and mutex file directory
    # for individual mutexes, or change the global defaults
    # Uncomment and change the directory if mutexes are file-based and the default
    # mutex file directory is not on a local disk or is not appropriate for some
    # other reason.
    # Mutex default:/run/httpd
    # Listen: Allows you to bind Apache to specific IP addresses and/or
    # ports, instead of the default. See also the <VirtualHost>
    # directive.
    # Change this to Listen on specific IP addresses as shown below to
    # prevent Apache from glomming onto all bound IP addresses.
    #Listen 12.34.56.78:80
    Listen 80
    # Dynamic Shared Object (DSO) Support
    # To be able to use the functionality of a module which was built as a DSO you
    # have to place corresponding `LoadModule' lines at this location so the
    # directives contained in it are actually available _before_ they are used.
    # Statically compiled modules (those listed by `httpd -l') do not need
    # to be loaded here.
    # Example:
    # LoadModule foo_module modules/mod_foo.so
    LoadModule authn_file_module modules/mod_authn_file.so
    #LoadModule authn_dbm_module modules/mod_authn_dbm.so
    #LoadModule authn_anon_module modules/mod_authn_anon.so
    #LoadModule authn_dbd_module modules/mod_authn_dbd.so
    #LoadModule authn_socache_module modules/mod_authn_socache.so
    LoadModule authn_core_module modules/mod_authn_core.so
    LoadModule authz_host_module modules/mod_authz_host.so
    LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
    LoadModule authz_user_module modules/mod_authz_user.so
    #LoadModule authz_dbm_module modules/mod_authz_dbm.so
    #LoadModule authz_owner_module modules/mod_authz_owner.so
    #LoadModule authz_dbd_module modules/mod_authz_dbd.so
    LoadModule authz_core_module modules/mod_authz_core.so
    #LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
    LoadModule access_compat_module modules/mod_access_compat.so
    LoadModule auth_basic_module modules/mod_auth_basic.so
    #LoadModule auth_form_module modules/mod_auth_form.so
    #LoadModule auth_digest_module modules/mod_auth_digest.so
    #LoadModule allowmethods_module modules/mod_allowmethods.so
    #LoadModule file_cache_module modules/mod_file_cache.so
    #LoadModule cache_module modules/mod_cache.so
    #LoadModule cache_disk_module modules/mod_cache_disk.so
    #LoadModule cache_socache_module modules/mod_cache_socache.so
    #LoadModule socache_shmcb_module modules/mod_socache_shmcb.so
    #LoadModule socache_dbm_module modules/mod_socache_dbm.so
    #LoadModule socache_memcache_module modules/mod_socache_memcache.so
    #LoadModule watchdog_module modules/mod_watchdog.so
    #LoadModule macro_module modules/mod_macro.so
    #LoadModule dbd_module modules/mod_dbd.so
    #LoadModule dumpio_module modules/mod_dumpio.so
    #LoadModule echo_module modules/mod_echo.so
    #LoadModule buffer_module modules/mod_buffer.so
    #LoadModule data_module modules/mod_data.so
    #LoadModule ratelimit_module modules/mod_ratelimit.so
    LoadModule reqtimeout_module modules/mod_reqtimeout.so
    #LoadModule ext_filter_module modules/mod_ext_filter.so
    #LoadModule request_module modules/mod_request.so
    LoadModule include_module modules/mod_include.so
    LoadModule filter_module modules/mod_filter.so
    #LoadModule reflector_module modules/mod_reflector.so
    #LoadModule substitute_module modules/mod_substitute.so
    #LoadModule sed_module modules/mod_sed.so
    #LoadModule charset_lite_module modules/mod_charset_lite.so
    #LoadModule deflate_module modules/mod_deflate.so
    #LoadModule xml2enc_module modules/mod_xml2enc.so
    #LoadModule proxy_html_module modules/mod_proxy_html.so
    LoadModule mime_module modules/mod_mime.so
    #LoadModule ldap_module modules/mod_ldap.so
    LoadModule log_config_module modules/mod_log_config.so
    #LoadModule log_debug_module modules/mod_log_debug.so
    #LoadModule log_forensic_module modules/mod_log_forensic.so
    #LoadModule logio_module modules/mod_logio.so
    #LoadModule lua_module modules/mod_lua.so
    LoadModule env_module modules/mod_env.so
    #LoadModule mime_magic_module modules/mod_mime_magic.so
    #LoadModule cern_meta_module modules/mod_cern_meta.so
    #LoadModule expires_module modules/mod_expires.so
    LoadModule headers_module modules/mod_headers.so
    #LoadModule ident_module modules/mod_ident.so
    #LoadModule usertrack_module modules/mod_usertrack.so
    #LoadModule unique_id_module modules/mod_unique_id.so
    LoadModule setenvif_module modules/mod_setenvif.so
    LoadModule version_module modules/mod_version.so
    #LoadModule remoteip_module modules/mod_remoteip.so
    LoadModule proxy_module modules/mod_proxy.so
    LoadModule proxy_connect_module modules/mod_proxy_connect.so
    LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
    LoadModule proxy_http_module modules/mod_proxy_http.so
    LoadModule proxy_fcgi_module modules/mod_proxy_fcgi.so
    LoadModule proxy_scgi_module modules/mod_proxy_scgi.so
    #LoadModule proxy_fdpass_module modules/mod_proxy_fdpass.so
    LoadModule proxy_wstunnel_module modules/mod_proxy_wstunnel.so
    LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
    LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
    LoadModule proxy_express_module modules/mod_proxy_express.so
    #LoadModule session_module modules/mod_session.so
    #LoadModule session_cookie_module modules/mod_session_cookie.so
    #LoadModule session_crypto_module modules/mod_session_crypto.so
    #LoadModule session_dbd_module modules/mod_session_dbd.so
    LoadModule slotmem_shm_module modules/mod_slotmem_shm.so
    #LoadModule slotmem_plain_module modules/mod_slotmem_plain.so
    #LoadModule ssl_module modules/mod_ssl.so
    #LoadModule dialup_module modules/mod_dialup.so
    LoadModule lbmethod_byrequests_module modules/mod_lbmethod_byrequests.so
    LoadModule lbmethod_bytraffic_module modules/mod_lbmethod_bytraffic.so
    LoadModule lbmethod_bybusyness_module modules/mod_lbmethod_bybusyness.so
    LoadModule lbmethod_heartbeat_module modules/mod_lbmethod_heartbeat.so
    LoadModule mpm_event_module modules/mod_mpm_event.so
    LoadModule unixd_module modules/mod_unixd.so
    #LoadModule heartbeat_module modules/mod_heartbeat.so
    #LoadModule heartmonitor_module modules/mod_heartmonitor.so
    #LoadModule dav_module modules/mod_dav.so
    LoadModule status_module modules/mod_status.so
    LoadModule autoindex_module modules/mod_autoindex.so
    #LoadModule asis_module modules/mod_asis.so
    #LoadModule info_module modules/mod_info.so
    #LoadModule suexec_module modules/mod_suexec.so
    #LoadModule cgid_module modules/mod_cgid.so
    #LoadModule cgi_module modules/mod_cgi.so
    #LoadModule dav_fs_module modules/mod_dav_fs.so
    #LoadModule dav_lock_module modules/mod_dav_lock.so
    #LoadModule vhost_alias_module modules/mod_vhost_alias.so
    LoadModule negotiation_module modules/mod_negotiation.so
    LoadModule dir_module modules/mod_dir.so
    #LoadModule imagemap_module modules/mod_imagemap.so
    #LoadModule actions_module modules/mod_actions.so
    #LoadModule speling_module modules/mod_speling.so
    LoadModule userdir_module modules/mod_userdir.so
    LoadModule alias_module modules/mod_alias.so
    #LoadModule rewrite_module modules/mod_rewrite.so
    #Load php5 module
    LoadModule php5_module modules/libphp5.so
    <IfModule unixd_module>
    # If you wish httpd to run as a different user or group, you must run
    # httpd as root initially and it will switch.
    # User/Group: The name (or #number) of the user/group to run httpd as.
    # It is usually good practice to create a dedicated user and group for
    # running httpd, as with most system services.
    User http
    Group http
    </IfModule>
    # 'Main' server configuration
    # The directives in this section set up the values used by the 'main'
    # server, which responds to any requests that aren't handled by a
    # <VirtualHost> definition. These values also provide defaults for
    # any <VirtualHost> containers you may define later in the file.
    # All of these directives may appear inside <VirtualHost> containers,
    # in which case these default settings will be overridden for the
    # virtual host being defined.
    # ServerAdmin: Your address, where problems with the server should be
    # e-mailed. This address appears on some server-generated pages, such
    # as error documents. e.g. [email protected]
    ServerAdmin [email protected]
    # ServerName gives the name and port that the server uses to identify itself.
    # This can often be determined automatically, but we recommend you specify
    # it explicitly to prevent problems during startup.
    # If your host doesn't have a registered DNS name, enter its IP address here.
    #ServerName www.example.com:80
    # Deny access to the entirety of your server's filesystem. You must
    # explicitly permit access to web content directories in other
    # <Directory> blocks below.
    <Directory />
    AllowOverride none
    Require all denied
    </Directory>
    # Note that from this point forward you must specifically allow
    # particular features to be enabled - so if something's not working as
    # you might expect, make sure that you have specifically enabled it
    # below.
    # DocumentRoot: The directory out of which you will serve your
    # documents. By default, all requests are taken from this directory, but
    # symbolic links and aliases may be used to point to other locations.
    DocumentRoot "/srv/http"
    <Directory "/srv/http">
    # Possible values for the Options directive are "None", "All",
    # or any combination of:
    # Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
    # Note that "MultiViews" must be named *explicitly* --- "Options All"
    # doesn't give it to you.
    # The Options directive is both complicated and important. Please see
    # http://httpd.apache.org/docs/2.4/mod/core.html#options
    # for more information.
    Options Indexes FollowSymLinks
    # AllowOverride controls what directives may be placed in .htaccess files.
    # It can be "All", "None", or any combination of the keywords:
    # AllowOverride FileInfo AuthConfig Limit
    AllowOverride None
    # Controls who can get stuff from this server.
    Require all granted
    </Directory>
    # DirectoryIndex: sets the file that Apache will serve if a directory
    # is requested.
    <IfModule dir_module>
    DirectoryIndex index.html
    </IfModule>
    # The following lines prevent .htaccess and .htpasswd files from being
    # viewed by Web clients.
    <Files ".ht*">
    Require all denied
    </Files>
    # ErrorLog: The location of the error log file.
    # If you do not specify an ErrorLog directive within a <VirtualHost>
    # container, error messages relating to that virtual host will be
    # logged here. If you *do* define an error logfile for a <VirtualHost>
    # container, that host's errors will be logged there and not here.
    ErrorLog "/var/log/httpd/error_log"
    # LogLevel: Control the number of messages logged to the error_log.
    # Possible values include: debug, info, notice, warn, error, crit,
    # alert, emerg.
    LogLevel warn
    <IfModule log_config_module>
    # The following directives define some format nicknames for use with
    # a CustomLog directive (see below).
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
    LogFormat "%h %l %u %t \"%r\" %>s %b" common
    <IfModule logio_module>
    # You need to enable mod_logio.c to use %I and %O
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
    </IfModule>
    # The location and format of the access logfile (Common Logfile Format).
    # If you do not define any access logfiles within a <VirtualHost>
    # container, they will be logged here. Contrariwise, if you *do*
    # define per-<VirtualHost> access logfiles, transactions will be
    # logged therein and *not* in this file.
    CustomLog "/var/log/httpd/access_log" common
    # If you prefer a logfile with access, agent, and referer information
    # (Combined Logfile Format) you can use the following directive.
    #CustomLog "/var/log/httpd/access_log" combined
    </IfModule>
    <IfModule alias_module>
    # Redirect: Allows you to tell clients about documents that used to
    # exist in your server's namespace, but do not anymore. The client
    # will make a new request for the document at its new location.
    # Example:
    # Redirect permanent /foo http://www.example.com/bar
    # Alias: Maps web paths into filesystem paths and is used to
    # access content that does not live under the DocumentRoot.
    # Example:
    # Alias /webpath /full/filesystem/path
    # If you include a trailing / on /webpath then the server will
    # require it to be present in the URL. You will also likely
    # need to provide a <Directory> section to allow access to
    # the filesystem path.
    # ScriptAlias: This controls which directories contain server scripts.
    # ScriptAliases are essentially the same as Aliases, except that
    # documents in the target directory are treated as applications and
    # run by the server when requested rather than as documents sent to the
    # client. The same rules about trailing "/" apply to ScriptAlias
    # directives as to Alias.
    ScriptAlias /cgi-bin/ "/srv/http/cgi-bin/"
    </IfModule>
    <IfModule cgid_module>
    # ScriptSock: On threaded servers, designate the path to the UNIX
    # socket used to communicate with the CGI daemon of mod_cgid.
    #Scriptsock cgisock
    </IfModule>
    # "/srv/http/cgi-bin" should be changed to whatever your ScriptAliased
    # CGI directory exists, if you have that configured.
    <Directory "/srv/http/cgi-bin">
    AllowOverride None
    Options None
    Require all granted
    </Directory>
    <IfModule mime_module>
    # TypesConfig points to the file containing the list of mappings from
    # filename extension to MIME-type.
    TypesConfig conf/mime.types
    # AddType allows you to add to or override the MIME configuration
    # file specified in TypesConfig for specific file types.
    #AddType application/x-gzip .tgz
    # AddEncoding allows you to have certain browsers uncompress
    # information on the fly. Note: Not all browsers support this.
    #AddEncoding x-compress .Z
    #AddEncoding x-gzip .gz .tgz
    # If the AddEncoding directives above are commented-out, then you
    # probably should define those extensions to indicate media types:
    AddType application/x-compress .Z
    AddType application/x-gzip .gz .tgz
    # AddHandler allows you to map certain file extensions to "handlers":
    # actions unrelated to filetype. These can be either built into the server
    # or added with the Action directive (see below)
    # To use CGI scripts outside of ScriptAliased directories:
    # (You will also need to add "ExecCGI" to the "Options" directive.)
    #AddHandler cgi-script .cgi
    # For type maps (negotiated resources):
    #AddHandler type-map var
    # Filters allow you to process content before it is sent to the client.
    # To parse .shtml files for server-side includes (SSI):
    # (You will also need to add "Includes" to the "Options" directive.)
    #AddType text/html .shtml
    #AddOutputFilter INCLUDES .shtml
    </IfModule>
    # The mod_mime_magic module allows the server to use various hints from the
    # contents of the file itself to determine its type. The MIMEMagicFile
    # directive tells the module where the hint definitions are located.
    #MIMEMagicFile conf/magic
    # Customizable error responses come in three flavors:
    # 1) plain text 2) local redirects 3) external redirects
    # Some examples:
    #ErrorDocument 500 "The server made a boo boo."
    #ErrorDocument 404 /missing.html
    #ErrorDocument 404 "/cgi-bin/missing_handler.pl"
    #ErrorDocument 402 http://www.example.com/subscription_info.html
    # MaxRanges: Maximum number of Ranges in a request before
    # returning the entire resource, or one of the special
    # values 'default', 'none' or 'unlimited'.
    # Default setting is to accept 200 Ranges.
    #MaxRanges unlimited
    # EnableMMAP and EnableSendfile: On systems that support it,
    # memory-mapping or the sendfile syscall may be used to deliver
    # files. This usually improves server performance, but must
    # be turned off when serving from networked-mounted
    # filesystems or if support for these functions is otherwise
    # broken on your system.
    # Defaults: EnableMMAP On, EnableSendfile Off
    #EnableMMAP off
    #EnableSendfile on
    # Supplemental configuration
    # The configuration files in the conf/extra/ directory can be
    # included to add extra features or to modify the default configuration of
    # the server, or you may simply copy their contents here and change as
    # necessary.
    # Server-pool management (MPM specific)
    Include conf/extra/httpd-mpm.conf
    # Multi-language error messages
    Include conf/extra/httpd-multilang-errordoc.conf
    # Fancy directory listings
    Include conf/extra/httpd-autoindex.conf
    # Language settings
    Include conf/extra/httpd-languages.conf
    # User home directories
    Include conf/extra/httpd-userdir.conf
    # Real-time info on requests and configuration
    #Include conf/extra/httpd-info.conf
    # Virtual hosts
    #Include conf/extra/httpd-vhosts.conf
    # Local access to the Apache HTTP Server Manual
    #Include conf/extra/httpd-manual.conf
    # Distributed authoring and versioning (WebDAV)
    #Include conf/extra/httpd-dav.conf
    # Various default settings
    Include conf/extra/httpd-default.conf
    # PHP settings
    Include conf/extra/php5_module.conf
    # Configure mod_proxy_html to understand HTML4/XHTML1
    <IfModule proxy_html_module>
    Include conf/extra/proxy-html.conf
    </IfModule>
    # Secure (SSL/TLS) connections
    #Include conf/extra/httpd-ssl.conf
    # Note: The following must must be present to support
    # starting without SSL on platforms with no /dev/random equivalent
    # but a statically compiled-in mod_ssl.
    <IfModule ssl_module>
    SSLRandomSeed startup builtin
    SSLRandomSeed connect builtin
    </IfModule>
    # uncomment out the below to deal with user agents that deliberately
    # violate open standards by misusing DNT (DNT *must* be a specific
    # end-user choice)
    #<IfModule setenvif_module>
    #BrowserMatch "MSIE 10.0;" bad_DNT
    #</IfModule>
    #<IfModule headers_module>
    #RequestHeader unset DNT env=bad_DNT
    #</IfModule>
    Thanks, sorry my english is bad .
    Last edited by Creaprog (2014-08-25 10:25:17)

    I just noticed the exact same thing. It turns out that the httpd-ssl.conf file on my system is still the old v2.2 syntax, which means that the SSLMutex directive is still in there. This is an invalid directive after 2.2.
    This is where things get interesting. At first, I simply thought I had forgotten to merge httpd-ssl.conf.pacnew after apache had been upgraded to 2.4. However, when I check my pacman.log, it appears that httpd-ssl.conf was never upgraded when apache went to 2.4 - (2.2.26-1 -> 2.4.7-1). There was never a pacnew file generated to be merged.
    I took a look at the apache package via the abs and the "proper" httpd-ssl.conf is certainly in there, so why pacman never created a pacnew file is a mystery.
    Anyway, to fix this: pull the httpd-ssl.conf from the apache package, either from your cache, using the abs and building it, or (I think) pacman may re-install it if you move the file to a backup location (not sure about this). Then merge your original httpd-ssl-conf with the new one.

  • Nvidia 8800 GT not the best for Aperture use?

    I've been reading from barefeats ( http://barefeats.com/harper10.html ) that the 8800 GT is not the best graphics card for Aperture. Actually I don't think they actually tested Aperture, but Motion 3. The Nvidia is a more expensive option than the ATIs, yet it would be worse for Aperture? Has someone specifically benchmarked Aperture 2 (not another pro app, and no synthetic tests of core image) with the 8800 GT against the other cards? Would Apple update Aperture to make it take better advantage of the 8800 GT's strengths (when available in a system)? I hope so. I already got the Nvidia, and am waiting to get a Mac Pro in the summer.

    Here's my prelim findings (as posted in another thread). Will come back with more detailed comments after I have a chance to test some more:
    Re: nvidia 8800GT in 1st generation MacPro
    Posted: 25-Apr-2008 13:08 in response to: Dale Strumpell
    Reply Email
    I've just put one in my first gen mac pro, too. I can confirm a great deal of improvement over the stock 7300 gt. My prob was when an image had been straightened, cropped etc if I then attempted edge sharpening it was just awful - beachballs in abundance, crappy panning, slower than Capture NX. Now, though, it is fast and pleasant to use. That's the good news. The bad news is either:
    1. Apple put such a puny graphics card in a Mac Pro (sic) in the first place (although it copes with everything except its own Pro photo software)
    2. Apple wrote such idiosyncratic software (leaning on the on-graphics card memory so much) that meant Mac Pro (sic) machines hardly more than a year old couldn't cope without a new graphics card when running Apple's own pro photo software. That and the 7300 is still on the "recommended" list of cards for running Aperture 2.
    Ho and, indeed, hum.
    Cheers
    D

  • Did up date for 10.7.4 to 10.7.5 and update for Aperture and now  Aperture doesn't open.  How do I fix?

    Did up date for 10.7.4 to 10.7.5 and update for Aperture and now  Aperture doesn't open.  How do I fix?

    I heard dump the app and reinstall?  How do I go about that?

  • Is there a way to save print job for later?

    Is there a way to have print jobs saved for a later date/time? The only solution I can think of is to save the document/web page/file to a folder (e.g., "print later"). However, I'd rather just be able to hit print and in the print dialogue "send" the job to a print queue that I can open later.
    For the curious, there are two often reoccuring situations where I want to save a print job for later: 1) I work late at night when my family is asleep and my house is not large enough to avoid disturbing their sleep by printing; and 2) I need to print out a 50+ page work document and I don't want to use my home computer to do it.
    I'll appreciate whatever tips, recommendations, thoughts I get.

    the method mentioned by benwiggy will certainly work.  If you want to an option that would give you more options, you could use a PDF Service.  You could then put a specific job on hold while still allowing others to use the printer.
    You can do this by opening AppleScript Editor (/Applications/Utilities).  You can copy and paste the following into an editor window --
    on open printJobs
    tell application "Finder"
    set trapFile to quoted form of POSIX path of (printJobs as string)
    end tell
    set defaultPrinter to do shell script "lpstat -d | awk -F: '{print $2}'"
    do shell script "lpr -P" & defaultPrinter & " -q " & trapFile
    end open
    Save the file as an Application.  You can name it something like Hold Print Job.  Then just put it in the PDF Services directory in the Library directory of your Home folder <yourname>/Library/PDF Services.  You may need to make the PDF Services directory as it may not already be there.
    Once the file is in place, you can use it by using the PDF drop down menu at the bottom left of a print window.  That will send the file to the printer and put it on hold.  Others can still use the printer.  You can then print your file whenever you want.  Just open the print queue as mentioned by benwiggy.  Highlight the job that is Paused.  You will see a little curly icon at the very right (looks like a reload icon in a web browser).  Just click that icon and the job will start printing.

  • BackGround Job for Transaction VF06

    Hi Experts,
    We are having problems with the background Job for transaction VF06. We run this job every day except weekends but this job runs and takes only 0 sec without creating Invoices.
    Allthough running this transaction Manually creates Invoice with same variant.
    Kindly help me on this.
    Thanks and Regards,
    Neha Kapoor

    Hi,
    I have the seen the Log it tells:
    Date       Time     Message text                                                                 Message class Message no. Message type
    29.06.2008 22:00:48 Job started                                                                       00           516          S
    29.06.2008 22:00:48 Step 001 started (program RV60SBAT, variant SOIE AUTO BILL, user ID GGBATCH)      00           550          S
    29.06.2008 22:00:48 Job finished                                                                      00           517          S
    But Invoices are not getting created.
    Thanks and Regards,
    Neha Kapoor

  • Program works but background job for that program fails....

    I have a requirement where I have to collect the details of the purchase order and put the details in XML file format and FTP the XML file to an external third party FTP Server.
    To realize this I developed a report program which follows following logic.
    1)     First I collected the PO details by calling the BAPI BAPI_PO_GETDETAIL1.
    2)     Then using the following link "/people/r.eijpe/blog/2005/11/10/xml-dom-processing-in-abap-part-i--convert-an-abap-table-into-xml-file-using-sap-dom-approach
    I converted these PO details to the XML file format that the third party people accept.
           In the code I used u201CCALL METHOD cl_gui_frontend_services=>gui_downloadu201D and in this process first the XML file is generated and is getting stored on my deskytop.
    3)     Then I called HTTP_SCRAMBLE, FTP_CONNECT, FTP_COMMAND , FTP_DISCONNECT and RFC_CONNECTION_CLOSE.
    This works perfectly well and each time I execute the report the file is getting FTPu2019ed to the third party FTP server.
    Now I tried to schedule a batch job for this and the batch job fails with follwing errors
    02/25/2009 15:08:47 Error in Control Framework
    Message Class  = FES         
    Message Number = 022  
    Message Type   = E
    02/25/2009 15:08:47 Job cancelled after system exception ERROR_MESSAGE 
    Message Class  = 00        
    Message Number = 564  
    Message Type   = A                
    Can some one tell me what is going wrong. My report works perfect in front end but fails if I try to schedule a background job for it in SM36.
    Can you please tell me whatz going wrong with batch job? Any Help is highly appreciated.
    Regards,
    JEssica SAm

    Robert...Thanks for the reply...
    I am using follwing code
    l_xml_size = l_ostream->get_num_written_raw( ).
        CALL METHOD cl_gui_frontend_services=>gui_download
          EXPORTING
            bin_filesize = l_xml_size
            filename     = FILEPATH
            filetype     = 'BIN'
          CHANGING
            data_tab     = l_xml_table
          EXCEPTIONS
            OTHERS       = 24.
        IF sy-subrc <> 0.
          MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                     WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    Now what changes should i make..where should i store my XML file then instead of my desktop?
    and whih Function Module should i Use..

  • Can ABAP proxy to consume WSDL file be run as background job for every10min

    Hi all,
    I have a requirement where I need to build an interface which gatheru2019s the purchase order details and send to external third party software in their required format (as an XML file).
    So I should be the first point of contact and should trigger the interface each time a purchase order is generated.
    So I am thinking that I should develop a background job for every 10 minutes which will look for new purchase orders and gathers the information of the purchase orders and send them to external third party software in their required format.
    I have gone through all the SAP forums and e-Learning but still I have confusion in regards to how is it possible technically? Can some one guide me with some information on the same.
    I have a little bit of confusion and want to know few things.
    1)     Should I create a web service or should I consume a web service?
    2)     If I need to consume a web service, then can I write an ABAP proxy to be run in background fro evry 10 minutes? I mean can we run ABAP proxy as a batch job in the background?
    3)     Is there a difference between consuming an XML file and WSDL File?
    Any Help will be highly appreciated.
    Regards,
    Jessica.

    There are two options (as I know) to generate XML file.
    1. Use XML TRANSFORMATION to get the XML string based your TRANSFORMATION. You can input your data and get back the XML string. Download this string to a file
    Test XML generation program is:
    types: begin of ty_data,
           num   type i,
           end   of ty_data.
    DATA: itab TYPE standard table of ty_Data,
          la_data like line of itab,
          xmlstr TYPE string.
    DO 3 TIMES.
      la_data-num = sy-index.
      APPEND la_data TO itab.
    ENDDO.
    CALL TRANSFORMATION ztest_np1
      SOURCE table = itab
      RESULT XML xmlstr.
    CALL FUNCTION 'DISPLAY_XML_STRING'
      EXPORTING xml_string = xmlstr.
    My ZTEST_NP1 transformation. To create a transformation, click on the transformation in the "CALL TRANSFORMATION ztest_np1" statement. Select Simple transformation type.
    <?sap.transform simple?>
    <tt:transform xmlns:tt="http://www.sap.com/transformation-templates">
      <tt:root name="table"/>
      <tt:template>
        <table>
          <tt:loop ref=".table">
            <item>
              <tt:value ref="NUM"/>
            </item>
          </tt:loop>
        </table>
      </tt:template>
    </tt:transform>
    XML string is like:
      <?xml version="1.0" encoding="utf-8" ?>
      <table>
      <item>1</item>
      <item>2</item>
      <item>3</item>
      </table>
    To use this option, you have to create a transformation and than use it to generate the XML string.
    Check this SAP Help
    http://help.sap.com/saphelp_nw04s/helpdata/en/e3/7d4719ca581441b6841f1054ff1326/frameset.htm
    2. You can concatenate and create an XML string and download that string into a file.
    Regards,
    Naimesh Patel

  • Error in Schedule Background Job for Deadline Monitoring of swu3

    While Auto Customization swu3 i am getting error message 'Output device "" not known' in 'Schedule Background Job for Deadline Monitoring'
    Please advice what could be cause of it

    the earlier problem of background job was solved by changing the  output device assigned to user wf-batch .
    regarding the transport request :
    when i was trying to execute the step : "Schedule bakgrd for missed deadlines " MANUEL it was giving me an option of SAVE AND SCHEDULE . which was creating the transport request . but when i executed it automatically it worked fine without asking a request to me ... i don't know why )-: ... probablly we can specify a different interval then the standard of three minutes and which will be transported (it's just a guess) . i have  executed it  automatically ...
    well thanks all for u r help

  • Problem in creating Batch job for programs in different servers.

    Hi All,
    I have a requirement like i have 2 different programs ( PRG1,PRG2 ) running in 3 different SAP servers (SER1,SER2,SER3).
    I want to create a batch job for the programs.
    Here When I run the PRG1 in Server SER1,it will create a file1 in SER1 as well as the other 2 servers (SER2 and SER3).
    It just create a file and there is no content in the file.Once i start writing records to file1in SER1,the same record will be started writing in SER2 and SER3.This is using PRG1.
    Once PRG1 will complete writing records in file,Next PRG2 will run in SER2 using file created by PRG1.
    I want to create a batch job for PRG1.
    How to trigger the PRG2 after completing job1 for PRG1 without any manual interaction.
    Please help me for this.

    Hi Ambili
    You can set steps in these jobs in transaction SM36.
    You can define that Job 2 starts after Job1 complete sucessfully and same game for other jobs.
    Please, check attachment for detailed information about that
    Kind regards
    Edited by: Carlos Machado on May 27, 2010 6:01 PM

  • Creating job for md03

    Hello,
    I'm looking for the ABAP program name of creating a job for MD03
    Could anyone help with this? Or just tell me how could I create a job for md03?
    Thank you

    Dear,
    Program SAPMM61X it is for MD01 MRp at plant level.
    For Back ground use the  RMMRP000
    Please refer this link,
    Re: MRP background job
    Regards,
    R.Brahmankar

  • Creating a job for a procedure with an input parameter

    Hi,
    I want to create a job for a procedure ( sp_proc ) with a input parameter.
    The input parameter is a date value.
    As per the syntax for dbms_job.submit procedure;
    dbms_job.submit (
    job IN BINARY_INTEGER,
    what IN VARCHAR2,
    next_date IN DATE,
    interval IN VARCHAR2 DEFAULT 'NULL',
    no_parse IN BOOLEAN DEFAULT FALSE);
    How should the procedure be declared in the 'what' parameter of the dbms_job.submit procedure ?
    Please guide.
    Thanks.

    Hi,
    You are wright, I have found this thread [DBMS_JOB -- how to pass parameters to the job|http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:351033761220].
    Regards,

  • Creating a Job for publication in Sql Server with select statement for passing a parameter

    I am creating a job for adding article to a publication.  the second step (e.g. for adding article) gives me error. I pass the name of the table as follow:
         EXEC sp_addarticle
               @publication = 'TTB', --THE NAME OF MY PUBLICATION
               'select top (1)' @article = 'Name from TableAdded Order by create_date Desc',
               'select top (1)' @source_object = 'Name from TableAdded Order by create_date Desc',
                @force_invalidate_snapshot = 1;
    TableAdded is a table I have in my publisher which contains the name of the newly added table.
    I believe it fails because the way I pass the name of the article to the store procedure is not correct. Can anyone please help me on that?
    Kind regards
    Amin

    Yes, the way you add article is wrong.
    you may try the below and let us know if you have any issues:
    while loop begin (Get the values from TableAdded with status IsAdded=0)
              Assign the values to variables like @article = Select top 1 Name from TableAdded where IsAdded=0
              Call the sp_addarticle assigning the variable
              update the Isadded flag in tableAdded for the name to 1 
     end while 
    BTB, Article configuration is supposed to be a one time configuration. Having said, you can easily configure through API. Caution, not sure what are you trying here, for adding new article, you may need to synch the data first in the above approach and should
    carried out in the downtime.

Maybe you are looking for