[SOLVED] ZSH - PATH problem when using script via udev rule

Shark82 · 11-07-2012, 02:11 AM

So, i have migrated to zsh and averything is fine except a little PATH problem. Now, i hava a power saving script that is executed when i unplug the power line (via udev rule). Till migration to zsh averything worked fine but when i changed #!/bin/bash to #!/bin/zsh in script, it doesn't work anymore. I found out that script is workable only if i write full paths in it, eg. /sbin/hdparm... instead of hdparm... When i am in terminal or console PATH variable is working fine. I also found out, for now, that the problem are commands in /sbin and /usr/sbin folder - commands in /usr/bin are working just fine.

My PATH:

Code:

/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/usr/bin/vendor_perl:/usr/bin/core_perl

My /etc/profile

Code:

# /etc/profile

#Set our umask
umask 022

# Set our default path

PATH="/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin"
export PATH

# Load profiles from /etc/profile.d
if test -d /etc/profile.d/; then
        for profile in /etc/profile.d/*.sh; do
                test -r "$profile" && . "$profile"
        done
        unset profile
fi

# Source global bash config
if test "$PS1" && test "$BASH" && test -r /etc/bash.bashrc; then
        . /etc/bash.bashrc
fi

# Termcap is outdated, old, and crusty, kill it.
unset TERMCAP

# Man is much better than us at figuring this out
unset MANPATH

My script:

Code:

#!/bin/zsh

case "$1" in
  true) # Enable power saving settings on battery
        # Device Runtime-PM
        #for dpcontrol in /sys/bus/{pci,spi,i2c}/devices/*/power/control; do echo auto > $dpcontrol; done
        # Disable nmi_watchdog
        echo 0 > /proc/sys/kernel/nmi_watchdog
        # kernel write mode
        echo 5 > /proc/sys/vm/laptop_mode
        echo 1500 > /proc/sys/vm/dirty_writeback_centisecs
        # disk powersave
        hdparm -S 36 -B 128 /dev/sda &> /dev/null
        for i in /sys/class/scsi_host/host*/link_power_management_policy; do echo min_power > $i; done
        # sound card powersave
        echo 60 > /sys/module/snd_hda_intel/parameters/power_save
        echo Y > /sys/module/snd_hda_intel/parameters/power_save_controller
        # wlan0 powersave
        iwconfig wlan0 power on
        # backlight
        echo 2 > /sys/class/backlight/acpi_video0/brightness
        ;;
  false) # Return to default on AC power
        # Device Runtime-PM
        #for dpcontrol in /sys/bus/{pci,spi,i2c}/devices/*/power/control; do echo on > $dpcontrol; done
        # Enable nmi_watchdog
        echo 1 > /proc/sys/kernel/nmi_watchdog
        # kernel write mode
        echo 0 > /proc/sys/vm/laptop_mode
        echo 500 > /proc/sys/vm/dirty_writeback_centisecs
        # disk powersave
        hdparm -S 0 -B 254 /dev/sda &> /dev/null
        for i in /sys/class/scsi_host/host*/link_power_management_policy; do echo max_performance > $i; done
        # sound card powersave
        echo 300 > /sys/module/snd_hda_intel/parameters/power_save
        echo Y > /sys/module/snd_hda_intel/parameters/power_save_controller
        # wlan0 powersave
        iwconfig wlan0 power off
        #backlight
        echo 13 > /sys/class/backlight/acpi_video0/brightness
        ;;
esac
exit 0

bigrigdriver · 11-07-2012, 07:59 PM

If you intend to keep using zsh, you should spend some time reading The ZSH User's Guide and creating your own .zsh and .zshenv files in your home directory. That alone may solve most of your problems when running scripts written for bash.

Zsh uses the $PATH variable, but is also uses a $path array, which is more flexible than using the PATH env variable.

The Zsh Guide discussion of PATH begins on page 47.

Excerpt:

Quote:

It helps to be able to ﬁnd external programmes, i.e. anything not part of the shell, any
command other than a builtin, function or alias. The $path array is used for this. Actually,
what the system needs is the environment variable $PATH, which contains a list of directories
in which to search for programmes, separated from each other by a colon. These directories
are the individual components of the array $path. So if $path contains
path=(/bin /usr/bin /usr/local/bin .)
then $PATH will automatically contain the effect of
PATH=/bin:/usr/bin:/usr/local/bin:.
without you having to set that. The idea is simply that, while the system needs $PATH
because it doesn’t understand arrays, it’s much more ﬂexible to be able to use arrays within
the shell and hence pretty much forget about the $PATH form.

Shark82 · 11-08-2012, 02:51 AM

Hi

I have solved the problem by creating file /etc/zsh/zshenv and write this down:

Code:

path=(/usr/local/bin /usr/bin /bin /usr/local/sbin /usr/sbin /sbin)

Thanks!

bigrigdriver · 11-08-2012, 06:13 AM

It would be better if you created file ~/.zshenv and put your corrections there. By having the corrections in /etc/zsh/zshenv, you risk losing the corrections every time zsh is updated.

Shark82 · 11-08-2012, 07:14 AM

You are right but there is one problem. I have a script that is executed by udev and this script is in /etc folder. If i move /etc/zsh/zshenc to ~/.zshenv the udev won't respect this paths in .zshenv.