Re: stdout and stdin in udev rule

On 2012-04-30 17:15:25 +0200, Anonymous Remailer (austria) said:

exec 2>/tmp/debug.output; set -x

the debug and key file are empty. This is a little bit strange

My udev rule shows:
SUBSYSTEMS=="usb", ATTRS{serial}=="the serial", ACTION=="add", SYMLINK+="luksdev", RUN+="/usr/local/bin/lukscmd openvolume"
and the script runs the dd command and the cryptsetup call with the pipe sign |.

Can the symbolic link or the device not be exists? So the script is run, before the device exists and dd returns in this case no values?




Relevant Pages

  • Re: fileevent and vwait dilema with one tcl script calling multiple copies of another
    ... pies of each script. ... loop *IS* the event loop and the 'main program' has no loop at all. ... # Event proc: file read event. ... proc Reader {pipe} { ...
  • accessing a pipe from TCL and C, hang in `close/exit
    ... I have a TCL shell script which opens a socket to some remote host, ... and opens a read-converter pipe. ... data arrives on the remote host. ... Now I want to close the channel from C++: ...
  • I can process my mail!
    ... I figured out how to pipe mail to my own scripts! ... the script as an argument. ... that won't confuse boundaries for message text. ... sendmail, but I'm not that interested in sendmail in particular. ...
  • Re: IO::Pipe and loss of data
    ... May be I cut too much, but as the last run of my big script was ... > show at least how I work to send a message and use the pipe. ... There is a fixed amount of buffer (probably 4K ... for each "server". ...
  • Re: how do i..
    ... On Sun, 2004-08-22 at 18:31, Mr. Oberoi wrote: ... > error results from the program(shell script) to a file. ... scriptname> filename 2>&1 ... the pipe character is used to "chain" the output of the command on ...