Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Expect command when triggered by launchd
Top Forums Shell Programming and Scripting Expect command when triggered by launchd Post 302734817 by rowie718 on Friday 23rd of November 2012 01:43:06 AM
Old 11-23-2012
Figured it out!

It wasnt anything about launchd session types or anything else. After reading a bit of the book "Exploring Expect", I followed up on a hint they gave about adding another expect line so the expect command doesnt end as soon as the first match is made and responded to. Here is the code that works, which is in a larger bash script:

Code:
/usr/bin/expect -c '
spawn slapconfig -backupdb "'"${recover}/_OD_Backup_${date}"'"
sleep 10
expect "Enter archive password:"
send "'"${passwd}\r"'"
expect "============"
' >${logfile}

For context, and hopefully to help other folks backing up mac servers, here is the larger bash script (which is a modified/updated older script I found online). It has been tested on 10.8.2 and works whether triggered via command line or launchdaemon (must be run as root). Adjust parameters at top of the script. The two variables with brackets (< and >) are required:

Code:
#!/bin/bash

# Path to the root folder where the backups will be stored
# This path should not be on the root volume, and not accessible
# to non-administrators

recover_path="<path/to/backup/folder>"

# Log file location

logfile="/Library/Logs/Server_Backup.log"

# You can either backup all of the services (even those not in use)
# or you can specify which services you want to backup.

# Path to serveradmin command

serveradmincmd="/Applications/Server.app/Contents/ServerRoot/usr/sbin/serveradmin"

services=`$serveradmincmd list`
#services="afp ipfilter smb"

# This is the password you will use to recover your OD sparseimage.
# It should NOT be the same as your Directory Administrator password
# for security reasons.

passwd="<password>"

# Number of days worth of backups to keep

backupdays="30"

###############################################################
#### Advanced modification only. The rest can be left as is ###
###############################################################

# This is the hostname of the server the script is running on
# This variable is used so that the same script can be run
# from multiple servers on a single share point
server=`hostname`

# Purge backups older than the amount of days user has set above

find "${recover_path}/$server/"* -maxdepth 0 -mtime +$backupdays -print | xargs rm

# Get today's date and format it as YYYYMMDD
date=`date ''+%c%m%d'' | awk '{printf $5}'`

# Set the full path to where this days backups will be stored
recover=${recover_path}/$server/$date

mkdir -p "${recover}"
chmod 600 "${recover}"

# grab the server configuration plists
for service in $services; do
    $serveradmincmd settings $service > "${recover}/$service.txt"
    sleep 1
done

# Backup Open Directory

/usr/bin/expect -c '
spawn slapconfig -backupdb "'"${recover}/_OD_Backup_${date}"'"
sleep 10
expect "Enter archive password:"
send "'"${passwd}\r"'"
expect "============"
' >${logfile}

echo "Script Complete at `date`" >>${logfile}
exit 0

 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Expect and auto expect command

I need to run a remote application(GUI) in a client.i.e on running a script in the client machine i should get the GUI application which is running in the server by providing password through the script.Will expect or autoexpect command suit for this scenario? could anyone help me by posting some... (0 Replies)
Discussion started by: arun_v
0 Replies

2. OS X (Apple)

interval in a launchd script

Hi, i'm planning a to automate my backup with a rsync user deamon in my launchd and let that run every 2 hours. my server contains a lot of video data which can expand rapidly , up to 1TB, in an interval of 2 hours. now i'm wondering what will happen when a rsync is running longer then the... (1 Reply)
Discussion started by: wessel
1 Replies

3. OS X (Apple)

[launchd] Creating a basic firewall

Hi, I'm trying to use launchd to detect whether certain ports are opened and if they are then to take some appropriate action, e.g. close the port or, worst case scenario, down the whole net connection. Apparently, force closing a port is not possible without killing the offending binary so... (3 Replies)
Discussion started by: ASGR
3 Replies

4. UNIX for Dummies Questions & Answers

Alert to be triggered

Hi, I need an alert to be triggered if any filesystem(imagine there are n no of filesystems) reaches more than 90%, it should send an alert to the mailbox stating which filesystem is at what percentage. How can I achieve this in unix? Many thanks. (8 Replies)
Discussion started by: venkatesht
8 Replies

5. Shell Programming and Scripting

Help with expect command

Hi, I am using following commands in my script to send a password to scp command. Everything is working fine except that I need a return code from the scp command. Do any one have an idea how to receive the exit code of scp command from expect. /usr/bin/expect << EOF spawn -noecho scp -pq... (0 Replies)
Discussion started by: pvamsikr
0 Replies

6. Shell Programming and Scripting

Expect command- need help

Hi All, I need help in making my script run perfectly as expected. This is a snippet from my script. I am trying to read the ";" from the below output using the expect command, but the command is not detecting it. Could you please help me correct the expect string? Snippet: ---- ---... (2 Replies)
Discussion started by: sonicj
2 Replies

7. UNIX for Dummies Questions & Answers

Launchd-owned processes unexpected behavior

Ok, so I have been struggling with this for a few days and I think I need an explanation of a few things before I go any further. I'm not sure it's possible to do what I'm trying, so before I pull my hair out, here is what I'm doing: I have written a program in LiveCode that sits on our... (2 Replies)
Discussion started by: nextyoyoma
2 Replies

8. Shell Programming and Scripting

Capture output of command triggered in background

Is there any way to trigger a sequence of commands in parallel and capture their output in variables? e.g. something on the following lines x=`echo "X" &` y=`echo "Y" &` z=`echo "Z" &` so that $x, $y, and $z evaluate to X, Y and Z res. (7 Replies)
Discussion started by: jawsnnn
7 Replies

9. Shell Programming and Scripting

Scripts triggered via 'expect' - stderr lost

I have a bash script on server that runs fine when run interactively and writes stderr output to a file. However, when invoked through a 'expect' script run on Mac OS my laptop which does ssh to the server : generates the expected file, but file has no content. I suspect the stderr is getting... (1 Reply)
Discussion started by: sdudc
1 Replies

10. Shell Programming and Scripting

Email need to be triggered

hi, Currently, in my code, the errors are written in log file. Additionally, i need to trigger the email of error captured. can we modify this script with email triggered along with existing command. echo "ERROR: $SCRIPT: $*" >>$LOGFILE (1 Reply)
Discussion started by: gowthamsoft
1 Replies

LEARN ABOUT DEBIAN

syslogout

SYSLOGOUT(8)						      System Manager's Manual						      SYSLOGOUT(8)

NAME

       syslogout - modular centralized shell logout mechanism

DESCRIPTION

       syslogout is a generic approach to enable centralized shell logout actions for all users of a given system in a modular and centralized way
       mostly aimed at avoiding work for lazy sysadmins.  It has only been tested to work with the bash shell.

       It basically consists of the small /etc/syslogout shell script which invokes other small shell scripts having a .bash suffix which are con-
       tained  in  the	/etc/syslogout.d/ directory.  The system administrator can drop in any script he wants without any naming convention other
       than that the scripts need to have a .bash suffix to enable automagic sourcing by the /etc/syslogout script.

       For shell sessions, the contents of /etc/syslogout.d/" will be sourced by every user at logout if the following lines are  present  in  his
       $HOME/.bash_logout:

	   if [ -f /etc/syslogout ]; then
	       . /etc/syslogout
	   fi

       If  used  for X sessions it is advisable to include the former statement into the Xreset script of the X display manager instead to prevent
       that closing of an terminal emulator window yields unexpected results in your running X session if your X11 terminal emulator  is  using  a
       login  shell.   Be  sure  then to run it under the user-id of the X session's user.  See the example files in /usr/share/doc/syslogout/ for
       illustration.

       Users not wanting /etc/syslogout to be sourced for their environment can easily disable it's automatic mechanism.  It can  be  disabled	by
       simply creating an empty file called $HOME/.nosyslogout in the user's home directory using e.g. the touch(1) command.

       Any single configuration file in /etc/syslogout.d/ can simply be overridden by any user by creating a private $HOME/.syslogout.d/ directory
       which may contain a user's own version of any configuration file to be sourced instead of the system default.   It's  names  have  just	to
       match  exactly  the  system's  default /etc/syslogout.d/ configuration files.  Empty versions of these files contained in the $HOME/.syslo-
       gout.d/ directory automatically disable sourcing of the system wide version.

       Naturally, users can add and include their own private scripts to be automagically executed by /etc/syslogout at logout time.

OPTIONS

       There are no options other than those dictated by shell conventions.  Anything is defined within the configuration scripts themselves.

SEE ALSO

       The  README  files  and	configuration  examples  contained  in	/usr/share/doc/syslogout/  and	the  manual  page  for	bash(1),  xdm(1x),
       xdm.options(5), and wdm(1x).  Recommended further reading is everything related with shell programming.

       If  you need a similar mechanism for executing code at login time check out the related package sysprofile(8) which is a very close compan-
       ion to syslogout.

BUGS

       syslogout in its current form is mainly restricted to bash(1) syntax.  In fact it is actually  a rather embarrassing quick and  dirty  hack
       than  anything  else  -	but  it  works.   It  serves the practical need to enable a centralized bash configuration  until something better
       becomes available.  Your constructive criticism in making  this	into something better" is very welcome.  Before i forget to mention it: we
       take patches... ;-)

AUTHOR

       syslogout  was developed by Paul Seelig <pseelig@debian.org> specifically for the Debian GNU/Linux system.  Feel free to port it to and use
       it anywhere else under the conditions of either the GNU public license or the BSD license or both.  Better yet, please help to make it into
       something more worthwhile than it currently is.

																      SYSLOGOUT(8)
All times are GMT -4. The time now is 02:08 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy