This seems to work,
Apparently the /b flag opens the program in the same console. I guess that means that mintty inherits the change. If I run this bat and enter "echo $PATH" in the terminal I get,
It appears as if the cygwin directories are in the path ( /usr/local/bin:/usr/bin: ). I have no real way of knowing if the is the correct /usr/local/bin since cygwin has truncated the path names.
The problem is that if I start a terminal from the normal shortcut (not using the bat file above) I get the same information when I echo $PATH. I also don't know if I need to start every terminal and every program from such a bat file.
I think it might make more sense to have the cygwin1 install location always be in the path as an environment variable since that is the one I use most often. If I need the cygwin2 install, I would need to run a bat file that would remove the cygwin1 install location from that path and then insert the cygwin2 install location for that session only.
I did a search and found lots of questions/comments about how a dos script could execute Unix but not the other way round. If it's possible, I'd like the link to a post/site that would show me the way.
Thanks. (4 Replies)
when i run in dos for example:
C: ls /temp
ls: cannot access /temp: No such file or directory
but when i run
C: ls \temp
windriver backup remotebackup
also when i run
C: ls temp
windriver backup remotebackup
The problems that i have all developpers scripts was written first like this... (0 Replies)
Hello ;
I have a problem running some script on dos .
when i run :
C: ls /temp
ls: cannot access /temp: No such file or directory
but when i run
C: ls \temp
windriver backup remotebackup
also when i run
C: ls temp
windriver backup remotebackup
The... (4 Replies)
Hi guys,
I need a *.bat to run a ksh file in the shell on Windows NT...nothing more :) How do I do it? I tried with the following but it failed:
set INFORMIXDIR=D:\user-applications\informix
set PATH=%INFORMIXDIR%;%PATH%
D:\user-applications\MKS\mksnt\sh.exe C:\hk_9.2\C3_weekly_auto.ksh... (4 Replies)
Hi,
(Apologies, I'm sure I'm not the first person to raise this question but so far in my searches haven't found a good answer).
I would like to output a listing per line of filename (including full path) and 'last updated' timestamp. e.g:
Z:\dir1\file1.txt 01/02/2010 10:43... (5 Replies)
1. What I am doing?
Building a DOS .bat file that will root my Droid 2 phone using adb commands in the .bat file. (Just for the fun of it and to help me learn "stuff".)
2. Problem:
Here are the problem steps to accomplish this task manually in an adb shell:
adb shell (Prompt is $)
cd... (2 Replies)
hi All, here is the problem: I'm not able to specify a PATH inside the user crontab file (/var/spool/cron/crontabs). The only syntax it accepts is the usual "* * * * * file" I'm not able to add PATH, or HOME, or MAILTO, or anything else. when I try to save the crontab, I have the error: ... (1 Reply)
I need to put/get files from Windows machine to Unix machine and vice-versa.
I wrote a text file "ftp1.txt" as below.
naga
naga06
cd /root/Naga
prom off
get time.unl
bye
I wrote another bat file "ftp.bat" as below.
ftp -n -s:C:\Users\Naga\Desktop\ftp1.txt IP_ADDRESS
but... (2 Replies)
Well I have a lot of scripts that require dragging and dropping files in order to define Source files etc.
However more often then not it is the case that the path to said file contains NUMEROUS spaces.
I know one way to evade this problem is to encase the path in Quotes like this:
... (7 Replies)
I'm curious to know how do I add an empty log file (test1.log) to an existing text file to monitor all the changes made to a.txt.
Is this expression
export PATH=$PATH:/home/test1.log
right to be added to the text file a.txt? (5 Replies)
Discussion started by: TestKing
5 Replies
LEARN ABOUT POSIX
systemd.environment-generator
SYSTEMD.ENVIRONMENT-GENERATOR(7) systemd.environment-generator SYSTEMD.ENVIRONMENT-GENERATOR(7)NAME
systemd.environment-generator - systemd environment file generators
SYNOPSIS
/lib/systemd/system-environment-generators/some-generator
/usr/lib/systemd/user-environment-generators/some-generator
/run/systemd/system-environment-generators/*
/etc/systemd/system-environment-generators/*
/usr/local/lib/systemd/system-environment-generators/*
/lib/systemd/system-environment-generators/*
/run/systemd/user-environment-generators/*
/etc/systemd/user-environment-generators/*
/usr/local/lib/systemd/user-environment-generators/*
/usr/lib/systemd/user-environment-generators/*
DESCRIPTION
Generators are small executables that live in /lib/systemd/system-environment-generators/ and other directories listed above. systemd(1)
will execute those binaries very early at the startup of each manager and at configuration reload time, before running the generators
described in systemd.generator(7) and before starting any units. Environment generators can override the environment that the manager
exports to services and other processes.
Generators are loaded from a set of paths determined during compilation, as listed above. System and user environment generators are loaded
from directories with names ending in system-environment-generators/ and user-environment-generators/, respectively. Generators found in
directories listed earlier override the ones with the same name in directories lower in the list. A symlink to /dev/null or an empty file
can be used to mask a generator, thereby preventing it from running. Please note that the order of the two directories with the highest
priority is reversed with respect to the unit load path, and generators in /run overwrite those in /etc.
After installing new generators or updating the configuration, systemctl daemon-reload may be executed. This will re-run all generators,
updating environment configuration. It will be used for any services that are started subsequently.
Environment file generators are executed similarly to unit file generators described in systemd.generator(7), with the following
differences:
o Generators are executed sequentially in the alphanumerical order of the final component of their name. The output of each generator
output is immediately parsed and used to update the environment for generators that run after that. Thus, later generators can use
and/or modify the output of earlier generators.
o Generators are run by every manager instance, their output can be different for each user.
It is recommended to use numerical prefixes for generator names to simplify ordering.
EXAMPLES
Example 1. A simple generator that extends an environment variable if a directory exists in the file system
# 50-xdg-data-dirs.sh
#!/bin/bash
# set the default value
XDG_DATA_DIRS="${XDG_DATA_DIRS:-/usr/local/share/:/usr/share}"
# add a directory if it exists
if [[ -d /opt/foo/share ]]; then
XDG_DATA_DIRS=/opt/foo/share:${XDG_DATA_DIRS}
fi
# write our output
echo XDG_DATA_DIRS=$XDG_DATA_DIRS
Example 2. A more complicated generator which reads existing configuration and mutates one variable
# 90-rearrange-path.py
#!/usr/bin/env python3
"""
Proof-of-concept systemd environment generator that makes sure that bin dirs
are always after matching sbin dirs in the path.
(Changes /sbin:/bin:/foo/bar to /bin:/sbin:/foo/bar.)
This generator shows how to override the configuration possibly created by
earlier generators. It would be easier to write in bash, but let's have it
in Python just to prove that we can, and to serve as a template for more
interesting generators.
"""
import os
import pathlib
def rearrange_bin_sbin(path):
"""Make sure any pair of .../bin, .../sbin directories is in this order
>>> rearrange_bin_sbin('/bin:/sbin:/usr/sbin:/usr/bin')
'/bin:/sbin:/usr/bin:/usr/sbin'
"""
items = [pathlib.Path(p) for p in path.split(':')]
for i in range(len(items)):
if 'sbin' in items[i].parts:
ind = items[i].parts.index('sbin')
bin = pathlib.Path(*items[i].parts[:ind], 'bin', *items[i].parts[ind+1:])
if bin in items[i+1:]:
j = i + 1 + items[i+1:].index(bin)
items[i], items[j] = items[j], items[i]
return ':'.join(p.as_posix() for p in items)
if __name__ == '__main__':
path = os.environ['PATH'] # This should be always set.
# If it's not, we'll just crash, we is OK too.
new = rearrange_bin_sbin(path)
if new != path:
print('PATH={}'.format(new))
Example 3. Debugging a generator
SYSTEMD_LOG_LEVEL=debug VAR_A=something VAR_B="something else"
/lib/systemd/system-environment-generators/path-to-generator
SEE ALSO systemd-environment-d-generator(8), systemd.generator(7), systemd(1), systemctl(1)systemd 237SYSTEMD.ENVIRONMENT-GENERATOR(7)